Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4dc94f575054bfdc32021d5aa1754e91a1aba3ae41dc10773b5ab80c2f4fb92

Tx prefix hash: e21beeb875d8180825383865815bfdae55ab6ccd6014231c77b6e79fbd69bd2a
Tx public key: bbc79945a3e9be1e8e2b3a7e589c721593a3cd904ddb47032e20e55275068fe7
Timestamp: 1708204954 Timestamp [UCT]: 2024-02-17 21:22:34 Age [y:d:h:m:s]: 01:042:20:12:53
Block: 959761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291651 RingCT/type: yes/0
Extra: 01bbc79945a3e9be1e8e2b3a7e589c721593a3cd904ddb47032e20e55275068fe702110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb8a952145967a555dcd7585bba19c9cb0a7e8148480121bb857c293d1db2c69 0.600000000000 1419314 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": 959771, "vin": [ { "gen": { "height": 959761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb8a952145967a555dcd7585bba19c9cb0a7e8148480121bb857c293d1db2c69" } } ], "extra": [ 1, 187, 199, 153, 69, 163, 233, 190, 30, 142, 43, 58, 126, 88, 156, 114, 21, 147, 163, 205, 144, 77, 219, 71, 3, 46, 32, 229, 82, 117, 6, 143, 231, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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