Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57021d82455c4eeb54538c45fb937ed113ce4c260f9076ad36f394aaf3047507

Tx prefix hash: 71f29125f6baebdacba2d1b6d73f3f911192816f513d9c17668464291b629111
Tx public key: a237339c28b04367d095b99fab0c7c06d805e724f7cd30e27d1e33e63a8c598d
Timestamp: 1704168214 Timestamp [UCT]: 2024-01-02 04:03:34 Age [y:d:h:m:s]: 01:055:01:34:40
Block: 926289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300433 RingCT/type: yes/0
Extra: 01a237339c28b04367d095b99fab0c7c06d805e724f7cd30e27d1e33e63a8c598d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c31e096c5ddb6b6e994fb96a8e037e67c2268ac207513ba9ef5d377cbe919ef 0.600000000000 1384067 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": 926299, "vin": [ { "gen": { "height": 926289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c31e096c5ddb6b6e994fb96a8e037e67c2268ac207513ba9ef5d377cbe919ef" } } ], "extra": [ 1, 162, 55, 51, 156, 40, 176, 67, 103, 208, 149, 185, 159, 171, 12, 124, 6, 216, 5, 231, 36, 247, 205, 48, 226, 125, 30, 51, 230, 58, 140, 89, 141, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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