Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39a27aae108334d0276ae126b49f13eea05e22c3ed019752f44d2181af2097d5

Tx prefix hash: 0c573b598bf08f7d641799de45c9ef59adca5648dbc357223da5b8f0d8ce4c7d
Tx public key: 83fd4fd31e6b3575a5b8ae36e55b483e0db4da09fe5b174486ef37f5381b7d3f
Timestamp: 1703553434 Timestamp [UCT]: 2023-12-26 01:17:14 Age [y:d:h:m:s]: 01:331:08:22:32
Block: 921205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495655 RingCT/type: yes/0
Extra: 0183fd4fd31e6b3575a5b8ae36e55b483e0db4da09fe5b174486ef37f5381b7d3f021100000004ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c15810a6bba539448a4e6669348a0f0e203adfe0f2731b88a4455137aac63a60 0.600000000000 1378891 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": 921215, "vin": [ { "gen": { "height": 921205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c15810a6bba539448a4e6669348a0f0e203adfe0f2731b88a4455137aac63a60" } } ], "extra": [ 1, 131, 253, 79, 211, 30, 107, 53, 117, 165, 184, 174, 54, 229, 91, 72, 62, 13, 180, 218, 9, 254, 91, 23, 68, 134, 239, 55, 245, 56, 27, 125, 63, 2, 17, 0, 0, 0, 4, 173, 86, 148, 172, 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