Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43400b9b5b2018d9985eb2918db03319022f8a92fd693310d6b319faebc27691

Tx prefix hash: 83a67f3ecea58d738e76aa9e12502bb918908397a3c5469493e5bb2c1f94331e
Tx public key: bdd920c801c21e47b85bf415bbf39009272b1c0d5f0f85df4faff3823146ab81
Timestamp: 1713491523 Timestamp [UCT]: 2024-04-19 01:52:03 Age [y:d:h:m:s]: 00:312:04:11:57
Block: 1003591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223146 RingCT/type: yes/0
Extra: 01bdd920c801c21e47b85bf415bbf39009272b1c0d5f0f85df4faff3823146ab81021100000004e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4b4556de60ab4a3d266c31628f022c112bc8f35fa7afa04ed7c9317c080b898 0.600000000000 1464133 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": 1003601, "vin": [ { "gen": { "height": 1003591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4b4556de60ab4a3d266c31628f022c112bc8f35fa7afa04ed7c9317c080b898" } } ], "extra": [ 1, 189, 217, 32, 200, 1, 194, 30, 71, 184, 91, 244, 21, 187, 243, 144, 9, 39, 43, 28, 13, 95, 15, 133, 223, 79, 175, 243, 130, 49, 70, 171, 129, 2, 17, 0, 0, 0, 4, 228, 187, 107, 131, 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