Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01ddcfa90f89131b9dde031a933f1d5503c2caa33ab6c69a06ca9dce96cd662a

Tx prefix hash: 49908ba78f596da8be9c2908ef5fb362c9bfd7e97f572295fe8d6d583746be13
Tx public key: 316e5bf68378f966a8217bd04377244d71ee14b804433a93565b5df0f2aae9a0
Timestamp: 1722154193 Timestamp [UCT]: 2024-07-28 08:09:53 Age [y:d:h:m:s]: 00:298:17:48:56
Block: 1075414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213463 RingCT/type: yes/0
Extra: 01316e5bf68378f966a8217bd04377244d71ee14b804433a93565b5df0f2aae9a0021100000013e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b888489052a0b241ad72b76bf2a5769fe7ecf539363c4a516dce40d44d501f0 0.600000000000 1547939 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": 1075424, "vin": [ { "gen": { "height": 1075414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b888489052a0b241ad72b76bf2a5769fe7ecf539363c4a516dce40d44d501f0" } } ], "extra": [ 1, 49, 110, 91, 246, 131, 120, 249, 102, 168, 33, 123, 208, 67, 119, 36, 77, 113, 238, 20, 184, 4, 67, 58, 147, 86, 91, 93, 240, 242, 170, 233, 160, 2, 17, 0, 0, 0, 19, 233, 20, 221, 21, 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