Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f81020df6b54cfbd064d8a32afad2e48d8768b5ea33d06b9348ede6ab39c6b40

Tx prefix hash: a5ff530d7a6f7d0b752e1277b510d25d6fb6f3205de3c00175ec167b98abf0d8
Tx public key: f9d9840c0001f1805a2f0b427f7300c306746c2de315c628e507041ce43c485c
Timestamp: 1695959821 Timestamp [UCT]: 2023-09-29 03:57:01 Age [y:d:h:m:s]: 01:206:10:54:25
Block: 858456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408609 RingCT/type: yes/0
Extra: 01f9d9840c0001f1805a2f0b427f7300c306746c2de315c628e507041ce43c485c0211000000034b8f5122000000000000000000

1 output(s) for total of 0.878170723000 dcy

stealth address amount amount idx
00: 7d91a6d4db38ea6b24ffd645b35a3811a7e7950e90c4a9cb88aaa6500cf75ed2 0.878170723000 1312632 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": 858466, "vin": [ { "gen": { "height": 858456 } } ], "vout": [ { "amount": 878170723, "target": { "key": "7d91a6d4db38ea6b24ffd645b35a3811a7e7950e90c4a9cb88aaa6500cf75ed2" } } ], "extra": [ 1, 249, 217, 132, 12, 0, 1, 241, 128, 90, 47, 11, 66, 127, 115, 0, 195, 6, 116, 108, 45, 227, 21, 198, 40, 229, 7, 4, 28, 228, 60, 72, 92, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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