Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6056f89f4d617fc39f83f44f22d6bd91064242510d6d64ba890d84274b357b4

Tx prefix hash: 65261cb9a5a3101584b198904fca28a9d19b9d1a31f430310cf0724c07c64c6a
Tx public key: bdb951dab00206637b0f5e3924debcefb1135aea2bac675f3a79dd64f3ff0497
Timestamp: 1660333832 Timestamp [UCT]: 2022-08-12 19:50:32 Age [y:d:h:m:s]: 02:087:14:11:41
Block: 564445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 584002 RingCT/type: yes/0
Extra: 01bdb951dab00206637b0f5e3924debcefb1135aea2bac675f3a79dd64f3ff049702110000000175e3f0e9000000000000000000

1 output(s) for total of 8.274838261000 dcy

stealth address amount amount idx
00: c254c1dc6a964ed586f31e7736b43e386896157a5dce35e561683f8aa9bf88b9 8.274838261000 997285 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": 564455, "vin": [ { "gen": { "height": 564445 } } ], "vout": [ { "amount": 8274838261, "target": { "key": "c254c1dc6a964ed586f31e7736b43e386896157a5dce35e561683f8aa9bf88b9" } } ], "extra": [ 1, 189, 185, 81, 218, 176, 2, 6, 99, 123, 15, 94, 57, 36, 222, 188, 239, 177, 19, 90, 234, 43, 172, 103, 95, 58, 121, 221, 100, 243, 255, 4, 151, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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