Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3b14bca6c6b42f08a6ae4bd538da95a21e43b1e012be6bbda3e20550a5f15a8e

Tx prefix hash: cc6aabe79de260fb4cfdcfb888faa667f4ffb1830f067d6625b883a19ad7649b
Tx public key: 73057cd55fbff2737c68aa7865c1a2af0c37eee8247482cac80d3160b5b8bb2f
Timestamp: 1637531358 Timestamp [UCT]: 2021-11-21 21:49:18 Age [y:d:h:m:s]: 03:100:21:45:46
Block: 379232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 850778 RingCT/type: yes/0
Extra: 0173057cd55fbff2737c68aa7865c1a2af0c37eee8247482cac80d3160b5b8bb2f02110000003b1cab2639000000000000000000

1 output(s) for total of 33.997527924000 dcy

stealth address amount amount idx
00: b2b92d97d6c5750a83ddc6cd7d84a2ee9f81d8a8d3bdeec4a62ebfe570a6038f 33.997527924000 766658 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 379242, "vin": [ { "gen": { "height": 379232 } } ], "vout": [ { "amount": 33997527924, "target": { "key": "b2b92d97d6c5750a83ddc6cd7d84a2ee9f81d8a8d3bdeec4a62ebfe570a6038f" } } ], "extra": [ 1, 115, 5, 124, 213, 95, 191, 242, 115, 124, 104, 170, 120, 101, 193, 162, 175, 12, 55, 238, 232, 36, 116, 130, 202, 200, 13, 49, 96, 181, 184, 187, 47, 2, 17, 0, 0, 0, 59, 28, 171, 38, 57, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8