Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2cf291e1c4245f504b1fca55ae7bc4f7c27cdb9055f4e4f0261fb26305fe685

Tx prefix hash: dc66e8f0c4ae1fb280f7f5c1e80054d2e0b27904fb6d38bb8c18d099a1da611f
Tx public key: bd37a60ef3a653d38874dc641eb11d5057bf3d55865665438e21f64c3da06f61
Timestamp: 1740613744 Timestamp [UCT]: 2025-02-26 23:49:04 Age [y:d:h:m:s]: 00:305:15:41:36
Block: 1227984 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216271 RingCT/type: yes/0
Extra: 01bd37a60ef3a653d38874dc641eb11d5057bf3d55865665438e21f64c3da06f610211000000111f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7272c209f3407c749c4b8d04602443524334deeedde7024d3440467e5c6b0d26 0.600000000000 1714861 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": 1227994, "vin": [ { "gen": { "height": 1227984 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7272c209f3407c749c4b8d04602443524334deeedde7024d3440467e5c6b0d26" } } ], "extra": [ 1, 189, 55, 166, 14, 243, 166, 83, 211, 136, 116, 220, 100, 30, 177, 29, 80, 87, 191, 61, 85, 134, 86, 101, 67, 142, 33, 246, 76, 61, 160, 111, 97, 2, 17, 0, 0, 0, 17, 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