Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c97be33d534c34490b7e60eabed4090e455fbcb85a64224168a86e8d0cb05ffa

Tx prefix hash: 66f0cbc8489dfa253e3ed5ebac11c6b8dc72583f39512ea424b08de345fc0cea
Tx public key: db523b3b1003722a1ff423f787c941f8d52fc005d1b27cf1550c8288f86ffda4
Timestamp: 1720764015 Timestamp [UCT]: 2024-07-12 06:00:15 Age [y:d:h:m:s]: 00:278:11:06:11
Block: 1063898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198935 RingCT/type: yes/0
Extra: 01db523b3b1003722a1ff423f787c941f8d52fc005d1b27cf1550c8288f86ffda4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b5a946d017a7938b103b7fa61e4ea594ed74daecdf5cf7abccf89d6ae9e04f4 0.600000000000 1534417 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": 1063908, "vin": [ { "gen": { "height": 1063898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b5a946d017a7938b103b7fa61e4ea594ed74daecdf5cf7abccf89d6ae9e04f4" } } ], "extra": [ 1, 219, 82, 59, 59, 16, 3, 114, 42, 31, 244, 35, 247, 135, 201, 65, 248, 213, 47, 192, 5, 209, 178, 124, 241, 85, 12, 130, 136, 248, 111, 253, 164, 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