Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b76c6d221bf7023f5e9cc328b6ad81413b21a945405b328b508b059227bcac4

Tx prefix hash: d048664504ed3aba246448733803b4f7174cea581820c7644bc49ebc47abccde
Tx public key: f94fc853122b71d8ea5a096f34a275ea8e27864924544a1b8cf3a6ddb48e31cd
Timestamp: 1578840266 Timestamp [UCT]: 2020-01-12 14:44:26 Age [y:d:h:m:s]: 04:357:07:09:17
Block: 44045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144823 RingCT/type: yes/0
Extra: 01f94fc853122b71d8ea5a096f34a275ea8e27864924544a1b8cf3a6ddb48e31cd0211000000234ac5aa02000000000000000000

1 output(s) for total of 438.592774547000 dcy

stealth address amount amount idx
00: 4f53cd0d46f7631008b7067f78d69ba4096623dbe3d077334d58210c16ebbb9e 438.592774547000 80013 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": 44055, "vin": [ { "gen": { "height": 44045 } } ], "vout": [ { "amount": 438592774547, "target": { "key": "4f53cd0d46f7631008b7067f78d69ba4096623dbe3d077334d58210c16ebbb9e" } } ], "extra": [ 1, 249, 79, 200, 83, 18, 43, 113, 216, 234, 90, 9, 111, 52, 162, 117, 234, 142, 39, 134, 73, 36, 84, 74, 27, 140, 243, 166, 221, 180, 142, 49, 205, 2, 17, 0, 0, 0, 35, 74, 197, 170, 2, 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