Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9be49e46f19da78ef60093c5c78ccf7bc812b5b7fcdd89041a1b64936564993d

Tx prefix hash: ec4fea27d165905df1ee24a46075c2dcde2896cb0eba08c4ed2c3b1c6648f563
Tx public key: 308642198685faac1e5bf50c869a704211a664523d096d088e4d9487c089f817
Timestamp: 1733516841 Timestamp [UCT]: 2024-12-06 20:27:21 Age [y:d:h:m:s]: 00:105:15:31:47
Block: 1169514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75302 RingCT/type: yes/0
Extra: 01308642198685faac1e5bf50c869a704211a664523d096d088e4d9487c089f8170211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd76f7f7f1181f6b38a53de53e67951b8c2730c49e2d0b0f5b1d498ba7652436 0.600000000000 1655233 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": 1169524, "vin": [ { "gen": { "height": 1169514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd76f7f7f1181f6b38a53de53e67951b8c2730c49e2d0b0f5b1d498ba7652436" } } ], "extra": [ 1, 48, 134, 66, 25, 134, 133, 250, 172, 30, 91, 245, 12, 134, 154, 112, 66, 17, 166, 100, 82, 61, 9, 109, 8, 142, 77, 148, 135, 192, 137, 248, 23, 2, 17, 0, 0, 0, 3, 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