Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de8078afc87a8060d250863118df383aaa436893e9086505bcd0f0e88f79408c

Tx prefix hash: 8fb7f0aca45b96e1daf70b7897fa68257b459d65a8b7b4984b72e4d2ade5fb33
Tx public key: b8e9fa9779fe5e852d851d9bddb17eb010d07753d261c9fdcc34d8cd946ef806
Timestamp: 1714559492 Timestamp [UCT]: 2024-05-01 10:31:32 Age [y:d:h:m:s]: 01:233:16:04:16
Block: 1012456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425687 RingCT/type: yes/0
Extra: 01b8e9fa9779fe5e852d851d9bddb17eb010d07753d261c9fdcc34d8cd946ef8060211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb3bd54cecdb66ffec4f2519e56f5462aaf964f3c5959d657b7377325ae64e23 0.600000000000 1474992 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": 1012466, "vin": [ { "gen": { "height": 1012456 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb3bd54cecdb66ffec4f2519e56f5462aaf964f3c5959d657b7377325ae64e23" } } ], "extra": [ 1, 184, 233, 250, 151, 121, 254, 94, 133, 45, 133, 29, 155, 221, 177, 126, 176, 16, 208, 119, 83, 210, 97, 201, 253, 204, 52, 216, 205, 148, 110, 248, 6, 2, 17, 0, 0, 0, 2, 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