Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b73db00de5eed7b32c9837e5416182f40333d15377ac88431a33622de0a7991

Tx prefix hash: 1a804295de700ba4b3cb2cdc1694c32a47d791165d0572025f01e269ed7b5d49
Tx public key: 22d71cb11c1ea5cebd31a249c5354c045b04086af67525503fef7617a0dd9b66
Timestamp: 1706526390 Timestamp [UCT]: 2024-01-29 11:06:30 Age [y:d:h:m:s]: 00:349:14:58:20
Block: 945832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250315 RingCT/type: yes/0
Extra: 0122d71cb11c1ea5cebd31a249c5354c045b04086af67525503fef7617a0dd9b6602110000000181d71d55000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd6e98f647020d4df5ab7f73afaeb9a273e9b0b99b76b45b1d01fed4cb343920 0.600000000000 1404156 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": 945842, "vin": [ { "gen": { "height": 945832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd6e98f647020d4df5ab7f73afaeb9a273e9b0b99b76b45b1d01fed4cb343920" } } ], "extra": [ 1, 34, 215, 28, 177, 28, 30, 165, 206, 189, 49, 162, 73, 197, 53, 76, 4, 91, 4, 8, 106, 246, 117, 37, 80, 63, 239, 118, 23, 160, 221, 155, 102, 2, 17, 0, 0, 0, 1, 129, 215, 29, 85, 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