Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42cabcb1f515fe4eb0b72e7396696a25cbc69431449987207d7b95c7333d5bca

Tx prefix hash: 415df7676d6c467acc860a10e03395e7900df6da43a6904b277b6efe3520c10b
Tx public key: b11b72cf21475cd9b397f11ef99d18f0c877ac4610ba21a68b4d2aca71c3f64b
Timestamp: 1710151789 Timestamp [UCT]: 2024-03-11 10:09:49 Age [y:d:h:m:s]: 00:349:06:38:23
Block: 975919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249705 RingCT/type: yes/0
Extra: 01b11b72cf21475cd9b397f11ef99d18f0c877ac4610ba21a68b4d2aca71c3f64b02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14a6f87ce18f55f0e15ee6c6f474d8147fd0c5a9156a230bf7e01a15fab9a522 0.600000000000 1435896 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": 975929, "vin": [ { "gen": { "height": 975919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14a6f87ce18f55f0e15ee6c6f474d8147fd0c5a9156a230bf7e01a15fab9a522" } } ], "extra": [ 1, 177, 27, 114, 207, 33, 71, 92, 217, 179, 151, 241, 30, 249, 157, 24, 240, 200, 119, 172, 70, 16, 186, 33, 166, 139, 77, 42, 202, 113, 195, 246, 75, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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