Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 508f52691091a795e3d94a8fd808dffce457315c7d74199ea5f6762b8eb9b184

Tx prefix hash: 03a7ab875766a3d134f81926c354c114aeea0b2b850089abc188df899d56e08e
Tx public key: 80c385c987e484e8d947a6b8a78a65f7746c104e526e9252417caeb90523f160
Timestamp: 1727623404 Timestamp [UCT]: 2024-09-29 15:23:24 Age [y:d:h:m:s]: 00:165:07:12:24
Block: 1120758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117949 RingCT/type: yes/0
Extra: 0180c385c987e484e8d947a6b8a78a65f7746c104e526e9252417caeb90523f16002110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 737436bed093b0a0d54fc30e8f13475984a926280085b3b012cfc027f95532fb 0.600000000000 1602787 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": 1120768, "vin": [ { "gen": { "height": 1120758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "737436bed093b0a0d54fc30e8f13475984a926280085b3b012cfc027f95532fb" } } ], "extra": [ 1, 128, 195, 133, 201, 135, 228, 132, 232, 217, 71, 166, 184, 167, 138, 101, 247, 116, 108, 16, 78, 82, 110, 146, 82, 65, 124, 174, 185, 5, 35, 241, 96, 2, 17, 0, 0, 0, 8, 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