Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b86e49ab9fa254381c80a09c6e98ec41ef40a63dca3a38275be637e3f061f3e1

Tx prefix hash: 080049d315540b2d52cbc7c6d49b3b21cd99f32997cc784210afe0c030058748
Tx public key: c6b3936c157e6eb7f2928f9500c8de9c2d3e7dba41121f685c7219e4f0521ecb
Timestamp: 1717330375 Timestamp [UCT]: 2024-06-02 12:12:55 Age [y:d:h:m:s]: 00:347:12:11:09
Block: 1035432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248367 RingCT/type: yes/0
Extra: 01c6b3936c157e6eb7f2928f9500c8de9c2d3e7dba41121f685c7219e4f0521ecb02110000000279bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a79fa7f640a5d1af81568d9e199bad2096e6f5f3f5d2c887cfac625e5d177be 0.600000000000 1503953 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": 1035442, "vin": [ { "gen": { "height": 1035432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a79fa7f640a5d1af81568d9e199bad2096e6f5f3f5d2c887cfac625e5d177be" } } ], "extra": [ 1, 198, 179, 147, 108, 21, 126, 110, 183, 242, 146, 143, 149, 0, 200, 222, 156, 45, 62, 125, 186, 65, 18, 31, 104, 92, 114, 25, 228, 240, 82, 30, 203, 2, 17, 0, 0, 0, 2, 121, 189, 163, 190, 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