Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53e3217f1a8703581f1be61d55924b76531099bec04be9d3f26b3a4a5c4cbc21

Tx prefix hash: 605e7fb4ac3fe284573c4e9542899fc25448468669ecfe43196a80e4ec703737
Tx public key: 8ad5555287549ea6b4c5e84eb5dbffe60d57c7c503af25a1c386baa6a1511e8b
Timestamp: 1704778216 Timestamp [UCT]: 2024-01-09 05:30:16 Age [y:d:h:m:s]: 01:164:10:05:37
Block: 931334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378515 RingCT/type: yes/0
Extra: 018ad5555287549ea6b4c5e84eb5dbffe60d57c7c503af25a1c386baa6a1511e8b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0b1d0fd0602005ca04e95fefe5026da1ee7faa42eec8e4160d6fd1e28c1e06c 0.600000000000 1389232 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": 931344, "vin": [ { "gen": { "height": 931334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0b1d0fd0602005ca04e95fefe5026da1ee7faa42eec8e4160d6fd1e28c1e06c" } } ], "extra": [ 1, 138, 213, 85, 82, 135, 84, 158, 166, 180, 197, 232, 78, 181, 219, 255, 230, 13, 87, 199, 197, 3, 175, 37, 161, 195, 134, 186, 166, 161, 81, 30, 139, 2, 17, 0, 0, 0, 2, 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