Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbe95e6c499fe3dfb5ebf9d628c640bf2adf695bfffa4dbac6d166bcfa1a9cd6

Tx prefix hash: 535c72dc8ed68d30b7677d20af647cc0a5cabceebd45b5073179bec395978a8d
Tx public key: d0554a8cd6b7f7aa6cae68735099ce15b8549fc74451398729a49b395f56141c
Timestamp: 1707510886 Timestamp [UCT]: 2024-02-09 20:34:46 Age [y:d:h:m:s]: 01:075:00:08:54
Block: 954007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314675 RingCT/type: yes/0
Extra: 01d0554a8cd6b7f7aa6cae68735099ce15b8549fc74451398729a49b395f56141c0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8cd235af13df46aef7dcd1c4df7df722236b1d0ab59ebae7af22a27d0f05ef7 0.600000000000 1413279 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": 954017, "vin": [ { "gen": { "height": 954007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8cd235af13df46aef7dcd1c4df7df722236b1d0ab59ebae7af22a27d0f05ef7" } } ], "extra": [ 1, 208, 85, 74, 140, 214, 183, 247, 170, 108, 174, 104, 115, 80, 153, 206, 21, 184, 84, 159, 199, 68, 81, 57, 135, 41, 164, 155, 57, 95, 86, 20, 28, 2, 17, 0, 0, 0, 5, 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