Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7eba5a01727acee7295a281f1d8f16ffac6a12126388693bea915cf0f540e9b8

Tx prefix hash: 12dc2a74b4d1ca31bdb7b36c9ae5995109d40f00c271908ab74379ab09610c14
Tx public key: 204f46ccd145821dc8183117d63b5defa3aa4ee3724bc7dcf51f966158262ce9
Timestamp: 1703344375 Timestamp [UCT]: 2023-12-23 15:12:55 Age [y:d:h:m:s]: 01:125:23:53:14
Block: 919471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351190 RingCT/type: yes/0
Extra: 01204f46ccd145821dc8183117d63b5defa3aa4ee3724bc7dcf51f966158262ce90211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36f37aecf435d5003cf1ca4350fbc9266a371db5e8c736bda052d892a8c9c804 0.600000000000 1377145 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": 919481, "vin": [ { "gen": { "height": 919471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36f37aecf435d5003cf1ca4350fbc9266a371db5e8c736bda052d892a8c9c804" } } ], "extra": [ 1, 32, 79, 70, 204, 209, 69, 130, 29, 200, 24, 49, 23, 214, 59, 93, 239, 163, 170, 78, 227, 114, 75, 199, 220, 245, 31, 150, 97, 88, 38, 44, 233, 2, 17, 0, 0, 0, 9, 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