Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e201f69e7f783febded640f4a4578b31e0dc1c8c214ff225834c73d2269b4b8

Tx prefix hash: 93d0e72c4937f4546f6b9dd6b9d6d0153ed07f7f6a7bdd1c2ce9b783a51113d4
Tx public key: fae9c3d070644be35749bb5da49b0cfdc34bdd3b6766c5ee9dca0207b6a0ba73
Timestamp: 1726569739 Timestamp [UCT]: 2024-09-17 10:42:19 Age [y:d:h:m:s]: 00:058:16:30:08
Block: 1112018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41943 RingCT/type: yes/0
Extra: 01fae9c3d070644be35749bb5da49b0cfdc34bdd3b6766c5ee9dca0207b6a0ba7302110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22e0a4e8e3104f7b2d01e5570874e5d105033b3d2698533c5eb6e27ca3e8fb7f 0.600000000000 1591185 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": 1112028, "vin": [ { "gen": { "height": 1112018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22e0a4e8e3104f7b2d01e5570874e5d105033b3d2698533c5eb6e27ca3e8fb7f" } } ], "extra": [ 1, 250, 233, 195, 208, 112, 100, 75, 227, 87, 73, 187, 93, 164, 155, 12, 253, 195, 75, 221, 59, 103, 102, 197, 238, 157, 202, 2, 7, 182, 160, 186, 115, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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