Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7abdc5d81ac532cd61476d809978461ef7494e5397d10c2125607bc27b132299

Tx prefix hash: 94ba96ddba39be5fb8779075828f6a1c270c3da80931cfd5a4c7ccbe21e9c9a7
Tx public key: ef101da9b1f27d6bb71a592a552c1f6efb86df5e4a71e90e2458821ec84e8149
Timestamp: 1708982097 Timestamp [UCT]: 2024-02-26 21:14:57 Age [y:d:h:m:s]: 01:034:22:36:47
Block: 966223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285963 RingCT/type: yes/0
Extra: 01ef101da9b1f27d6bb71a592a552c1f6efb86df5e4a71e90e2458821ec84e814902110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f276dcd34a17c7fac91a7bbd616c02c9b991b4992fd58ee98d05f29c57932192 0.600000000000 1425980 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": 966233, "vin": [ { "gen": { "height": 966223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f276dcd34a17c7fac91a7bbd616c02c9b991b4992fd58ee98d05f29c57932192" } } ], "extra": [ 1, 239, 16, 29, 169, 177, 242, 125, 107, 183, 26, 89, 42, 85, 44, 31, 110, 251, 134, 223, 94, 74, 113, 233, 14, 36, 88, 130, 30, 200, 78, 129, 73, 2, 17, 0, 0, 0, 10, 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