Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cb6a3a2c4c7e0937be336a7bda9867ffe3bd0609d28e3c7ec5c5529315ee398

Tx prefix hash: 3a110962c4f99852bc3d83baa9dd6cd76349e3e0799ce11082a3bb1d044a1a5e
Tx public key: 83da220674e9110283f1902d4c40a5ab628cfd53cbaee9c5a6cd4ffeb1753740
Timestamp: 1721646904 Timestamp [UCT]: 2024-07-22 11:15:04 Age [y:d:h:m:s]: 00:331:21:25:17
Block: 1071204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237034 RingCT/type: yes/0
Extra: 0183da220674e9110283f1902d4c40a5ab628cfd53cbaee9c5a6cd4ffeb175374002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f88c2482323af7bae0f26bdb888775a2af027040d062c9d5833c455d7fb3563d 0.600000000000 1543339 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": 1071214, "vin": [ { "gen": { "height": 1071204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f88c2482323af7bae0f26bdb888775a2af027040d062c9d5833c455d7fb3563d" } } ], "extra": [ 1, 131, 218, 34, 6, 116, 233, 17, 2, 131, 241, 144, 45, 76, 64, 165, 171, 98, 140, 253, 83, 203, 174, 233, 197, 166, 205, 79, 254, 177, 117, 55, 64, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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