Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9a40b184c58eadc62cec8c2e7dc94424432fe6be98db36bc2ef6c30ae36cedd

Tx prefix hash: 660a1b4a64be5082401cbc855ed29bfe9e166d566096ba9342f9eb2b78506cbb
Tx public key: 9a4c69375011dbb37fa6e1dd296cc736a615a386f70a0b9a3cd3a3492d7bd205
Timestamp: 1714497601 Timestamp [UCT]: 2024-04-30 17:20:01 Age [y:d:h:m:s]: 00:289:00:14:31
Block: 1011939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206580 RingCT/type: yes/0
Extra: 019a4c69375011dbb37fa6e1dd296cc736a615a386f70a0b9a3cd3a3492d7bd2050211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9be0a70c1e831793ced323141fb6da1e6f3a9ca9708e83583c98b1de82c90b01 0.600000000000 1474305 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": 1011949, "vin": [ { "gen": { "height": 1011939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9be0a70c1e831793ced323141fb6da1e6f3a9ca9708e83583c98b1de82c90b01" } } ], "extra": [ 1, 154, 76, 105, 55, 80, 17, 219, 179, 127, 166, 225, 221, 41, 108, 199, 54, 166, 21, 163, 134, 247, 10, 11, 154, 60, 211, 163, 73, 45, 123, 210, 5, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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