Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 357cf0aa9d1750bfc1509c11606b73f64e07397fde1722e39abb6359adea8a1e

Tx prefix hash: 05856d1b1dfa015a6e28bb364c5b9f968d70168f696996a03faad1494496b30c
Tx public key: 3b67b8e2ae70f301a7dc2cbb531d85ca572fe8a0fd1a2fe71ef6a89838d7d503
Timestamp: 1680576397 Timestamp [UCT]: 2023-04-04 02:46:37 Age [y:d:h:m:s]: 01:294:04:52:14
Block: 731513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471201 RingCT/type: yes/0
Extra: 013b67b8e2ae70f301a7dc2cbb531d85ca572fe8a0fd1a2fe71ef6a89838d7d503021100000001b3164c24000000000000000000

1 output(s) for total of 2.313097801000 dcy

stealth address amount amount idx
00: 755d7a99cda12a422d9af6d07b90a85b8e4a30d7024acb49ec67a336345ae77b 2.313097801000 1177296 of 0

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": 731523, "vin": [ { "gen": { "height": 731513 } } ], "vout": [ { "amount": 2313097801, "target": { "key": "755d7a99cda12a422d9af6d07b90a85b8e4a30d7024acb49ec67a336345ae77b" } } ], "extra": [ 1, 59, 103, 184, 226, 174, 112, 243, 1, 167, 220, 44, 187, 83, 29, 133, 202, 87, 47, 232, 160, 253, 26, 47, 231, 30, 246, 168, 152, 56, 215, 213, 3, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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