Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70570e619c07d0272c7ac83cf5043b5dc564bd7da2df7bad738e2a8c25acc479

Tx prefix hash: 8e817a523df43735207eb21174cfc1aed7b474171937f8f8ce7ebc6178237348
Tx public key: b96af217d704325f4e0f8324160e3d70ab8bb8f8075a6b45dbd4cf7631e9c26a
Timestamp: 1718314009 Timestamp [UCT]: 2024-06-13 21:26:49 Age [y:d:h:m:s]: 00:290:17:21:01
Block: 1043578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207748 RingCT/type: yes/0
Extra: 01b96af217d704325f4e0f8324160e3d70ab8bb8f8075a6b45dbd4cf7631e9c26a0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85714987105144bede8b2c7616989cc5724d60bb1ffa2a86d7fd143fb986bac4 0.600000000000 1512733 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": 1043588, "vin": [ { "gen": { "height": 1043578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85714987105144bede8b2c7616989cc5724d60bb1ffa2a86d7fd143fb986bac4" } } ], "extra": [ 1, 185, 106, 242, 23, 215, 4, 50, 95, 78, 15, 131, 36, 22, 14, 61, 112, 171, 139, 184, 248, 7, 90, 107, 69, 219, 212, 207, 118, 49, 233, 194, 106, 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