Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1fc0a6830b14ae382b825e89f39c27ac81e11a71014c3be63e5b5bac0aa8440

Tx prefix hash: a2770cd09dee83424c5dc1a00e679ae60f03dbca1037ff8131caa1898153feed
Tx public key: 753ca47130efd51dca1e9d7be0a7697f9ae8ea9570c7cfac94c39ce6db34532e
Timestamp: 1664370837 Timestamp [UCT]: 2022-09-28 13:13:57 Age [y:d:h:m:s]: 03:034:08:27:03
Block: 597486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 804715 RingCT/type: yes/0
Extra: 01753ca47130efd51dca1e9d7be0a7697f9ae8ea9570c7cfac94c39ce6db34532e021100000002798ce684000000000000000000

1 output(s) for total of 6.431035653000 dcy

stealth address amount amount idx
00: 6758e6176c98d3cc9b0a82e680936711ee10981ee3021d9f596cb9291a5159b2 6.431035653000 1032885 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": 597496, "vin": [ { "gen": { "height": 597486 } } ], "vout": [ { "amount": 6431035653, "target": { "key": "6758e6176c98d3cc9b0a82e680936711ee10981ee3021d9f596cb9291a5159b2" } } ], "extra": [ 1, 117, 60, 164, 113, 48, 239, 213, 29, 202, 30, 157, 123, 224, 167, 105, 127, 154, 232, 234, 149, 112, 199, 207, 172, 148, 195, 156, 230, 219, 52, 83, 46, 2, 17, 0, 0, 0, 2, 121, 140, 230, 132, 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