Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 683a259515e004bd99cac85ba74fc0a0a2decfd2392cb139d25498aff07afd87

Tx prefix hash: a5aa0e1e042ee072aaf5471213460157b1d7e39850cf4dc6f5295b41763527a2
Tx public key: cbdd104f0a3de01bd6aac3a3f2fa28d264fc01404ead4a1d7404552b46bc9a32
Timestamp: 1726236856 Timestamp [UCT]: 2024-09-13 14:14:16 Age [y:d:h:m:s]: 00:184:12:44:45
Block: 1109259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131716 RingCT/type: yes/0
Extra: 01cbdd104f0a3de01bd6aac3a3f2fa28d264fc01404ead4a1d7404552b46bc9a32021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a095c1aae976b17775390827674ade91219d34495f47a9074d9f70aaf59d490 0.600000000000 1587446 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": 1109269, "vin": [ { "gen": { "height": 1109259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a095c1aae976b17775390827674ade91219d34495f47a9074d9f70aaf59d490" } } ], "extra": [ 1, 203, 221, 16, 79, 10, 61, 224, 27, 214, 170, 195, 163, 242, 250, 40, 210, 100, 252, 1, 64, 78, 173, 74, 29, 116, 4, 85, 43, 70, 188, 154, 50, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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