Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 965fea11256a228b39cbcf3af3ec06949fb714a93b9898b4d6e328321c149a9a

Tx prefix hash: 5717b8f5a316cedeee04f4f3bfb84d3c175e752f0878f3daf714d6d9608144b1
Tx public key: dc32100f9fdcc4800006ea07b122ae469d716380d78eae95efb8c7f7852b442c
Timestamp: 1724601048 Timestamp [UCT]: 2024-08-25 15:50:48 Age [y:d:h:m:s]: 00:247:22:05:29
Block: 1095700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177065 RingCT/type: yes/0
Extra: 01dc32100f9fdcc4800006ea07b122ae469d716380d78eae95efb8c7f7852b442c02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b4904dda2324f5bd51a5cdc96f875c3b6b8c042c4f7e7d613f9edf28bc03d0e 0.600000000000 1570881 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": 1095710, "vin": [ { "gen": { "height": 1095700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b4904dda2324f5bd51a5cdc96f875c3b6b8c042c4f7e7d613f9edf28bc03d0e" } } ], "extra": [ 1, 220, 50, 16, 15, 159, 220, 196, 128, 0, 6, 234, 7, 177, 34, 174, 70, 157, 113, 99, 128, 215, 142, 174, 149, 239, 184, 199, 247, 133, 43, 68, 44, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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