Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f8945c3adb99a8894024dc6b9cf81759f6113c5f855486afb36caf26f4a338c

Tx prefix hash: 34378e4c5a92f9b3d403cd165a6bfe50b51ce6e1552a47248d6f34542a0527ec
Tx public key: 132ec0576abfa6a94974e83d5b96122d9caacb03a3875c5fd4f6a1b4ce168127
Timestamp: 1722775503 Timestamp [UCT]: 2024-08-04 12:45:03 Age [y:d:h:m:s]: 00:172:13:55:23
Block: 1080560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123425 RingCT/type: yes/0
Extra: 01132ec0576abfa6a94974e83d5b96122d9caacb03a3875c5fd4f6a1b4ce16812702110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 372abc6aac35d1c83a12179aef529ba7f2b4a888843b1a82c3e437e720193d55 0.600000000000 1553971 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": 1080570, "vin": [ { "gen": { "height": 1080560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "372abc6aac35d1c83a12179aef529ba7f2b4a888843b1a82c3e437e720193d55" } } ], "extra": [ 1, 19, 46, 192, 87, 106, 191, 166, 169, 73, 116, 232, 61, 91, 150, 18, 45, 156, 170, 203, 3, 163, 135, 92, 95, 212, 246, 161, 180, 206, 22, 129, 39, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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