Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2b4a60b39ed36f58ec63971d99c575a86cd31c4539dde5d6ee66302ed7771b0

Tx prefix hash: 3b16f8754a2d3f4ae256d4075dbb6912fa221cd3c07741aaceeb5fb1f0d92bad
Tx public key: 2230444cf8373bbd5c8bf0b1f9bc99e711ad51e9a733e30609ab717ff4fc4641
Timestamp: 1712064851 Timestamp [UCT]: 2024-04-02 13:34:11 Age [y:d:h:m:s]: 01:048:05:16:19
Block: 991739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295489 RingCT/type: yes/0
Extra: 012230444cf8373bbd5c8bf0b1f9bc99e711ad51e9a733e30609ab717ff4fc46410211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9deba02d463c79d0d8a6ff78fa54bf305eb0337e014a61514e96676dbf9b600b 0.600000000000 1452075 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": 991749, "vin": [ { "gen": { "height": 991739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9deba02d463c79d0d8a6ff78fa54bf305eb0337e014a61514e96676dbf9b600b" } } ], "extra": [ 1, 34, 48, 68, 76, 248, 55, 59, 189, 92, 139, 240, 177, 249, 188, 153, 231, 17, 173, 81, 233, 167, 51, 227, 6, 9, 171, 113, 127, 244, 252, 70, 65, 2, 17, 0, 0, 0, 5, 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