Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c926f1a46a76e281a678b28bd328fa8d2b6f765832dd8b8752562625e6b3f2c0

Tx prefix hash: b367d7b48b74567358671d5e4cf15ff093d7b070c567080c40f28036ed7badeb
Tx public key: 88ef3a6ea16e279d7545e229121a5fd0901d770848faf19f50a7db981c8ae1e0
Timestamp: 1699360207 Timestamp [UCT]: 2023-11-07 12:30:07 Age [y:d:h:m:s]: 01:150:05:03:44
Block: 886444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368548 RingCT/type: yes/0
Extra: 0188ef3a6ea16e279d7545e229121a5fd0901d770848faf19f50a7db981c8ae1e002110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.709321381000 dcy

stealth address amount amount idx
00: c69057de38ec4667a104aa684fcc68c21a8660a672de78673c17084d04f210e9 0.709321381000 1342263 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": 886454, "vin": [ { "gen": { "height": 886444 } } ], "vout": [ { "amount": 709321381, "target": { "key": "c69057de38ec4667a104aa684fcc68c21a8660a672de78673c17084d04f210e9" } } ], "extra": [ 1, 136, 239, 58, 110, 161, 110, 39, 157, 117, 69, 226, 41, 18, 26, 95, 208, 144, 29, 119, 8, 72, 250, 241, 159, 80, 167, 219, 152, 28, 138, 225, 224, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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