Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a64e04ab9524e934aa96dc516760c23069922e0c8a252a807a0eee68c01238a1

Tx prefix hash: aca8f03266f2e522eeac6369f89debd5a326c56e9a0ac9998348eb4e5c86bcea
Tx public key: 73e566574389ba9666135c2ab4e4f97c582f1466b8d3728d59eadb239ea83108
Timestamp: 1696189582 Timestamp [UCT]: 2023-10-01 19:46:22 Age [y:d:h:m:s]: 01:024:20:38:50
Block: 860358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279015 RingCT/type: yes/0
Extra: 0173e566574389ba9666135c2ab4e4f97c582f1466b8d3728d59eadb239ea831080211000000064b8f5122000000000000000000

1 output(s) for total of 0.865519458000 dcy

stealth address amount amount idx
00: 32c24c64bc1e0d1b79d594cc0e28ff6df33d43f010d3164534dfd162ef58ca21 0.865519458000 1314638 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": 860368, "vin": [ { "gen": { "height": 860358 } } ], "vout": [ { "amount": 865519458, "target": { "key": "32c24c64bc1e0d1b79d594cc0e28ff6df33d43f010d3164534dfd162ef58ca21" } } ], "extra": [ 1, 115, 229, 102, 87, 67, 137, 186, 150, 102, 19, 92, 42, 180, 228, 249, 124, 88, 47, 20, 102, 184, 211, 114, 141, 89, 234, 219, 35, 158, 168, 49, 8, 2, 17, 0, 0, 0, 6, 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