Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d02266d0ebc53b0b86a8080f7477477fe7079c2ab275f16bf1e57cb23373b866

Tx prefix hash: 011c8bc13d1e693250651c8ae31dabffd98795ed83a817bc66ff946682d0c8bb
Tx public key: dd0ce2c7f41d6c9e0e2427ed0538f3b2b249b282d5e945b0ae8b2381835e5078
Timestamp: 1703444866 Timestamp [UCT]: 2023-12-24 19:07:46 Age [y:d:h:m:s]: 01:325:04:51:49
Block: 920311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491267 RingCT/type: yes/0
Extra: 01dd0ce2c7f41d6c9e0e2427ed0538f3b2b249b282d5e945b0ae8b2381835e507802110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de7fcf0bd7e8e382d2d486cff25a9790d78e09fea47a80f5d67e44e62e3e6a72 0.600000000000 1377989 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": 920321, "vin": [ { "gen": { "height": 920311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de7fcf0bd7e8e382d2d486cff25a9790d78e09fea47a80f5d67e44e62e3e6a72" } } ], "extra": [ 1, 221, 12, 226, 199, 244, 29, 108, 158, 14, 36, 39, 237, 5, 56, 243, 178, 178, 73, 178, 130, 213, 233, 69, 176, 174, 139, 35, 129, 131, 94, 80, 120, 2, 17, 0, 0, 0, 11, 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