Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c96f492275a1bce5973fee7f2a20f7b19905542c5e7f338962814aed5a6c71a

Tx prefix hash: a2e1152b93d48cfc9a4e6c60c2a3c6b09da7af330013649347cdd749741a856f
Tx public key: 3a9d555ce40838f8ea59c722e73050a79652dfad4bf1286ded38db9fd2a7de01
Timestamp: 1712250955 Timestamp [UCT]: 2024-04-04 17:15:55 Age [y:d:h:m:s]: 00:346:19:14:59
Block: 993285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247984 RingCT/type: yes/0
Extra: 013a9d555ce40838f8ea59c722e73050a79652dfad4bf1286ded38db9fd2a7de0102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2801ab97d4714d4105c0ab5b32af5801ba82bf6b80440196edbebbb2bf87a5e 0.600000000000 1453671 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": 993295, "vin": [ { "gen": { "height": 993285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2801ab97d4714d4105c0ab5b32af5801ba82bf6b80440196edbebbb2bf87a5e" } } ], "extra": [ 1, 58, 157, 85, 92, 228, 8, 56, 248, 234, 89, 199, 34, 231, 48, 80, 167, 150, 82, 223, 173, 75, 241, 40, 109, 237, 56, 219, 159, 210, 167, 222, 1, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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