Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c36a45c2ecc62922d0d3fa5d9d8c8f60d252bb7099c3d6ee51fcdafd16b1a9d1

Tx prefix hash: 8a21bba16f521e9b4ecc273bce672076c2571349a885b626095987699a65efa3
Tx public key: 1ed24c6a6d8805d1f69208057f912be7b1d9350555be8dac5f94346d79756fc3
Timestamp: 1700927607 Timestamp [UCT]: 2023-11-25 15:53:27 Age [y:d:h:m:s]: 01:165:10:06:32
Block: 899434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379408 RingCT/type: yes/0
Extra: 011ed24c6a6d8805d1f69208057f912be7b1d9350555be8dac5f94346d79756fc302110000000475e3f0e9000000000000000000

1 output(s) for total of 0.642394434000 dcy

stealth address amount amount idx
00: d53633d7a002c9868c5995699137cdcfae193b7ccf3071580d42d0bc826e893d 0.642394434000 1355889 of 0

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": 899444, "vin": [ { "gen": { "height": 899434 } } ], "vout": [ { "amount": 642394434, "target": { "key": "d53633d7a002c9868c5995699137cdcfae193b7ccf3071580d42d0bc826e893d" } } ], "extra": [ 1, 30, 210, 76, 106, 109, 136, 5, 209, 246, 146, 8, 5, 127, 145, 43, 231, 177, 217, 53, 5, 85, 190, 141, 172, 95, 148, 52, 109, 121, 117, 111, 195, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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