Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33425ca2db6ed2ae4fbb9a8822e4c099a6241410a43963eccb7974183bd5afc5

Tx prefix hash: 1a8b970c8d218a11d043c086673dba6d06822ec97c14a6c3cafc8c64e4c0bfbd
Tx public key: 6b1d9e81ec915a3f48a2e964a6e17bf9bb67c30874734c14aa79b80cb3edaf03
Timestamp: 1712936364 Timestamp [UCT]: 2024-04-12 15:39:24 Age [y:d:h:m:s]: 01:032:11:59:50
Block: 998972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284212 RingCT/type: yes/0
Extra: 016b1d9e81ec915a3f48a2e964a6e17bf9bb67c30874734c14aa79b80cb3edaf030211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 936689c29bfa4e45e445c7665dbf17ec944e45384a923d3a61cb64257df09fb3 0.600000000000 1459448 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": 998982, "vin": [ { "gen": { "height": 998972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "936689c29bfa4e45e445c7665dbf17ec944e45384a923d3a61cb64257df09fb3" } } ], "extra": [ 1, 107, 29, 158, 129, 236, 145, 90, 63, 72, 162, 233, 100, 166, 225, 123, 249, 187, 103, 195, 8, 116, 115, 76, 20, 170, 121, 184, 12, 179, 237, 175, 3, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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