Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e07a9abb36fe66273820d3a378d08b2909b6b3ba512f0f952e45cb9d8705a1bf

Tx prefix hash: c629454f0273012b4b6a13882e75dbae9e6a9a97ced8c261dc429ae3fc8ac32c
Tx public key: cd269353213df06e11e65fb0a13fdf24c06284d41c2878c4545ef6c726370a08
Timestamp: 1577879121 Timestamp [UCT]: 2020-01-01 11:45:21 Age [y:d:h:m:s]: 04:322:10:47:46
Block: 36311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119674 RingCT/type: yes/0
Extra: 01cd269353213df06e11e65fb0a13fdf24c06284d41c2878c4545ef6c726370a080211000000f0e39b962a000000000000000000

1 output(s) for total of 465.251130009000 dcy

stealth address amount amount idx
00: 8d226b4e3c311704fad9e104fcb67fa52645ffc02524363791dacbd58d91d505 465.251130009000 61480 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": 36321, "vin": [ { "gen": { "height": 36311 } } ], "vout": [ { "amount": 465251130009, "target": { "key": "8d226b4e3c311704fad9e104fcb67fa52645ffc02524363791dacbd58d91d505" } } ], "extra": [ 1, 205, 38, 147, 83, 33, 61, 240, 110, 17, 230, 95, 176, 161, 63, 223, 36, 192, 98, 132, 212, 28, 40, 120, 196, 84, 94, 246, 199, 38, 55, 10, 8, 2, 17, 0, 0, 0, 240, 227, 155, 150, 42, 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