Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6006466928c5657068a079e3801d95e5bcf0b687c29930ad67f6d1be13ba6a8b

Tx prefix hash: 33ead27574e26609a09ed60c63d19b8cceaf9a2e0fb7a9572e32fde99f549718
Tx public key: 0d3c0211ab72a0f1f38b1318e6327ef6490b46dc6a29e8173f96f51819ad6568
Timestamp: 1734258593 Timestamp [UCT]: 2024-12-15 10:29:53 Age [y:d:h:m:s]: 00:132:10:25:09
Block: 1175673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94441 RingCT/type: yes/0
Extra: 010d3c0211ab72a0f1f38b1318e6327ef6490b46dc6a29e8173f96f51819ad65680211000000021f0a53eb000000000000000000

1 output(s) for total of 0.605790000000 dcy

stealth address amount amount idx
00: 0444508c712d40dadb61825410c0bdb7c00a6fede5727ad328912579b93bb804 0.605790000000 1661986 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": 1175683, "vin": [ { "gen": { "height": 1175673 } } ], "vout": [ { "amount": 605790000, "target": { "key": "0444508c712d40dadb61825410c0bdb7c00a6fede5727ad328912579b93bb804" } } ], "extra": [ 1, 13, 60, 2, 17, 171, 114, 160, 241, 243, 139, 19, 24, 230, 50, 126, 246, 73, 11, 70, 220, 106, 41, 232, 23, 63, 150, 245, 24, 25, 173, 101, 104, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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