Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39860aece6a3aea27010b0353827d487dafbaa58e90081717efe98d830a67783

Tx prefix hash: 949bc8ec6032c9ca2fcc6966636026ade665b8a438d874564d0374bb4581ef3e
Tx public key: b4b646f7fe0037e27b9f69945c96591c6a996cc09fb4a22f1e8e5c3ba8c4fe1d
Timestamp: 1684409844 Timestamp [UCT]: 2023-05-18 11:37:24 Age [y:d:h:m:s]: 02:175:19:44:47
Block: 762747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645459 RingCT/type: yes/0
Extra: 01b4b646f7fe0037e27b9f69945c96591c6a996cc09fb4a22f1e8e5c3ba8c4fe1d021100000007faf35c9c000000000000000000

1 output(s) for total of 1.822647743000 dcy

stealth address amount amount idx
00: b3302bb94fd50c4ac006bc75786131392071105784ba8eed02618a2de4d11e48 1.822647743000 1211516 of 0

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": 762757, "vin": [ { "gen": { "height": 762747 } } ], "vout": [ { "amount": 1822647743, "target": { "key": "b3302bb94fd50c4ac006bc75786131392071105784ba8eed02618a2de4d11e48" } } ], "extra": [ 1, 180, 182, 70, 247, 254, 0, 55, 226, 123, 159, 105, 148, 92, 150, 89, 28, 106, 153, 108, 192, 159, 180, 162, 47, 30, 142, 92, 59, 168, 196, 254, 29, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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