Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db017e1a5394133c0f6250364850e0a7eaeefbf8173f7138c5d393d75bc04906

Tx prefix hash: accbc6a4f03fb680233d5ee3f404530e636a8837952d00cc4af26cfd062c4a28
Tx public key: ff037b26cbde22b45946f90c571450c3c7a25e732a575b92f3e1db5ef8987beb
Timestamp: 1706323752 Timestamp [UCT]: 2024-01-27 02:49:12 Age [y:d:h:m:s]: 01:139:07:59:20
Block: 944143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360647 RingCT/type: yes/0
Extra: 01ff037b26cbde22b45946f90c571450c3c7a25e732a575b92f3e1db5ef8987beb0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4e9bce57cb2a4adabe63d50caf731c9bb1a71838f701d5cc65859cc13d76a97 0.600000000000 1402373 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": 944153, "vin": [ { "gen": { "height": 944143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4e9bce57cb2a4adabe63d50caf731c9bb1a71838f701d5cc65859cc13d76a97" } } ], "extra": [ 1, 255, 3, 123, 38, 203, 222, 34, 180, 89, 70, 249, 12, 87, 20, 80, 195, 199, 162, 94, 115, 42, 87, 91, 146, 243, 225, 219, 94, 248, 152, 123, 235, 2, 17, 0, 0, 0, 3, 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