Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38eb14c037254aaee5290c2d551e68e2ed619de0647c186352e1cc3e490b49ba

Tx prefix hash: 8c2b4391d326badb22f2ae6ea40647fe2303644b3ae6ad8e9e4129ec37176099
Tx public key: 01aa5481be2de6b35c9ed3cf4fdb8eb3898e13f580e188ccd011ed2cfdf62e3b
Timestamp: 1734139340 Timestamp [UCT]: 2024-12-14 01:22:20 Age [y:d:h:m:s]: 00:132:12:41:09
Block: 1174682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94519 RingCT/type: yes/0
Extra: 0101aa5481be2de6b35c9ed3cf4fdb8eb3898e13f580e188ccd011ed2cfdf62e3b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f586754ffd0cbbfe10d69e3177e7941fbfe7144dbee82a9c3767f530dbd42de 0.600000000000 1660867 of 15

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": 1174692, "vin": [ { "gen": { "height": 1174682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f586754ffd0cbbfe10d69e3177e7941fbfe7144dbee82a9c3767f530dbd42de" } } ], "extra": [ 1, 1, 170, 84, 129, 190, 45, 230, 179, 92, 158, 211, 207, 79, 219, 142, 179, 137, 142, 19, 245, 128, 225, 136, 204, 208, 17, 237, 44, 253, 246, 46, 59, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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