Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea33c64ca8a4d5faac6a06d6ea549b34706b4bf8606d0eab66b3e75850517306

Tx prefix hash: 842abedc2c455cc8affab36d5a93af6a5f4422f513ddd4709b217f8a96f7bc98
Tx public key: 9f7e3cd9ff20afe32730780e3d23107f6065bbb5d126b5ceb1682d3501e136c2
Timestamp: 1706937464 Timestamp [UCT]: 2024-02-03 05:17:44 Age [y:d:h:m:s]: 01:063:03:49:18
Block: 949246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306206 RingCT/type: yes/0
Extra: 019f7e3cd9ff20afe32730780e3d23107f6065bbb5d126b5ceb1682d3501e136c20211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f338b4c365447ab640769185c64098a11f280cc226b1e273683af72edfad3a9 0.600000000000 1407768 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": 949256, "vin": [ { "gen": { "height": 949246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f338b4c365447ab640769185c64098a11f280cc226b1e273683af72edfad3a9" } } ], "extra": [ 1, 159, 126, 60, 217, 255, 32, 175, 227, 39, 48, 120, 14, 61, 35, 16, 127, 96, 101, 187, 181, 209, 38, 181, 206, 177, 104, 45, 53, 1, 225, 54, 194, 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