Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 063c0cddfbd10db18352199026db9019f9a07419308e4cb6cac67147e19e43b6

Tx prefix hash: 9911add814215e34bb8d0bbe44efad396ae4e3e396b33aad081fb5c6699bebc0
Tx public key: 0efd9f874db73c7a018bc7c36966aba9cf6a8f8d38a7425b0861b69a4887b3ee
Timestamp: 1734757020 Timestamp [UCT]: 2024-12-21 04:57:00 Age [y:d:h:m:s]: 00:130:07:45:05
Block: 1179805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92924 RingCT/type: yes/0
Extra: 010efd9f874db73c7a018bc7c36966aba9cf6a8f8d38a7425b0861b69a4887b3ee021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea4d7c305e224db3930edeaee29aa18eed7a07eea05cd8e6b01c300265c65b55 0.600000000000 1666204 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": 1179815, "vin": [ { "gen": { "height": 1179805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea4d7c305e224db3930edeaee29aa18eed7a07eea05cd8e6b01c300265c65b55" } } ], "extra": [ 1, 14, 253, 159, 135, 77, 183, 60, 122, 1, 139, 199, 195, 105, 102, 171, 169, 207, 106, 143, 141, 56, 167, 66, 91, 8, 97, 182, 154, 72, 135, 179, 238, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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