Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbaa80fd9c58f6014f4c7742fd8f26aa07af1b693a02636b82463c19c0bc18d6

Tx prefix hash: 66d43bc445efae55bc86f9c6922385c215030839af1cdc207a464b1e741c611f
Tx public key: 935fe9bbb4998b741e54e44588696b7346ce63f74cf25802fa0ae02f40197904
Timestamp: 1719043430 Timestamp [UCT]: 2024-06-22 08:03:50 Age [y:d:h:m:s]: 00:273:02:43:59
Block: 1049608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195172 RingCT/type: yes/0
Extra: 01935fe9bbb4998b741e54e44588696b7346ce63f74cf25802fa0ae02f4019790402110000000b91fab441000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8aeb42e2d94ef0b99eaf2ea7e72a4564edc3260ada8d6a1b1a5655d7c7edd7d6 0.600000000000 1519709 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": 1049618, "vin": [ { "gen": { "height": 1049608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aeb42e2d94ef0b99eaf2ea7e72a4564edc3260ada8d6a1b1a5655d7c7edd7d6" } } ], "extra": [ 1, 147, 95, 233, 187, 180, 153, 139, 116, 30, 84, 228, 69, 136, 105, 107, 115, 70, 206, 99, 247, 76, 242, 88, 2, 250, 10, 224, 47, 64, 25, 121, 4, 2, 17, 0, 0, 0, 11, 145, 250, 180, 65, 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