Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 710c9097cd7d722adf6d11a7db447ad6dd0f630025e813776b36a176cff181cb

Tx prefix hash: e538ec20b031895433d9f3ad61ed2da1cf2a15537e24dae87a482545a82d1ff0
Tx public key: ebd4cfb3202cae077ec100e5b39e26993c858ded5f21e3c0cb1cfe7511ff89c8
Timestamp: 1674395824 Timestamp [UCT]: 2023-01-22 13:57:04 Age [y:d:h:m:s]: 02:129:01:16:26
Block: 680347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 613932 RingCT/type: yes/0
Extra: 01ebd4cfb3202cae077ec100e5b39e26993c858ded5f21e3c0cb1cfe7511ff89c802110000000183600029000000000000000000

1 output(s) for total of 3.418352525000 dcy

stealth address amount amount idx
00: 9b639713838c7e3a9e0269718b053f7a513f0caed5ca135227181124c49d5152 3.418352525000 1122378 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": 680357, "vin": [ { "gen": { "height": 680347 } } ], "vout": [ { "amount": 3418352525, "target": { "key": "9b639713838c7e3a9e0269718b053f7a513f0caed5ca135227181124c49d5152" } } ], "extra": [ 1, 235, 212, 207, 179, 32, 44, 174, 7, 126, 193, 0, 229, 179, 158, 38, 153, 60, 133, 141, 237, 95, 33, 227, 192, 203, 28, 254, 117, 17, 255, 137, 200, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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