Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4803c316b2fad551b1bb6dcf2ebf9d2ece9f050df0287ef5fd10f71472d3330e

Tx prefix hash: e0b3f012ab99fbadd99368770dbd91b812b909016d534b44ab8e716dc3bc8227
Tx public key: 990e8a0e80d6b197834e4f5289196abba0b8b9670d9a422b5534f91945f3fb0f
Timestamp: 1681120511 Timestamp [UCT]: 2023-04-10 09:55:11 Age [y:d:h:m:s]: 01:311:04:27:44
Block: 735464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 483681 RingCT/type: yes/0
Extra: 01990e8a0e80d6b197834e4f5289196abba0b8b9670d9a422b5534f91945f3fb0f02110000000174b6d784000000000000000000

1 output(s) for total of 2.244412541000 dcy

stealth address amount amount idx
00: 3ae8925f7b3950ec5e686b03c0a8c044d756c0034f0d63e5c1f8c722413afe7a 2.244412541000 1181793 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": 735474, "vin": [ { "gen": { "height": 735464 } } ], "vout": [ { "amount": 2244412541, "target": { "key": "3ae8925f7b3950ec5e686b03c0a8c044d756c0034f0d63e5c1f8c722413afe7a" } } ], "extra": [ 1, 153, 14, 138, 14, 128, 214, 177, 151, 131, 78, 79, 82, 137, 25, 106, 187, 160, 184, 185, 103, 13, 154, 66, 43, 85, 52, 249, 25, 69, 243, 251, 15, 2, 17, 0, 0, 0, 1, 116, 182, 215, 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