Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c481caff2080024bc2af015fea75503e6274f01e190db06f0914badd57c3831

Tx prefix hash: c2f7fb058c6c07a44e11b6f0a1845d27a02ffd1a16e811e370302a3615202e6b
Tx public key: 78ca847ffc5da52e6b4b2347596fe0d3472a535cb40076726ab8a5f31163e1a6
Timestamp: 1703470310 Timestamp [UCT]: 2023-12-25 02:11:50 Age [y:d:h:m:s]: 01:326:21:11:39
Block: 920530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492457 RingCT/type: yes/0
Extra: 0178ca847ffc5da52e6b4b2347596fe0d3472a535cb40076726ab8a5f31163e1a602110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b67d4dd1134c0002a70e0ad167280ab6818a273d410cc51a77dad6d1dbac0ea 0.600000000000 1378210 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": 920540, "vin": [ { "gen": { "height": 920530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b67d4dd1134c0002a70e0ad167280ab6818a273d410cc51a77dad6d1dbac0ea" } } ], "extra": [ 1, 120, 202, 132, 127, 252, 93, 165, 46, 107, 75, 35, 71, 89, 111, 224, 211, 71, 42, 83, 92, 180, 0, 118, 114, 106, 184, 165, 243, 17, 99, 225, 166, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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