Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d47d3cc6855131c9091089b75917f26388eb6f83a422cd8ff409be7d1d78c716

Tx prefix hash: d27e680441549796142bec9100af293bdfb8d5405ef6c922adb4d31e2bb4bdd9
Tx public key: ec126cb0c78d2ba6bfa109ad0c3f71946a35cbed4a1d01c84fdd09736cc2e00c
Timestamp: 1709045041 Timestamp [UCT]: 2024-02-27 14:44:01 Age [y:d:h:m:s]: 01:298:01:04:35
Block: 966745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471787 RingCT/type: yes/0
Extra: 01ec126cb0c78d2ba6bfa109ad0c3f71946a35cbed4a1d01c84fdd09736cc2e00c0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 021bc1d27929c6d035aa1c842d0c46d00e9d180762678196fd0c1653ee013a36 0.600000000000 1426516 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": 966755, "vin": [ { "gen": { "height": 966745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "021bc1d27929c6d035aa1c842d0c46d00e9d180762678196fd0c1653ee013a36" } } ], "extra": [ 1, 236, 18, 108, 176, 199, 141, 43, 166, 191, 161, 9, 173, 12, 63, 113, 148, 106, 53, 203, 237, 74, 29, 1, 200, 79, 221, 9, 115, 108, 194, 224, 12, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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