Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6a6166368a740f33ca7ecaf061494151c5b4bab9e62dfbfb505b31488e2fa46

Tx prefix hash: 555feb1a134881ba4d025cb67c633ff0cb462401ae6aff43144f946dcddce975
Tx public key: 57d7e0a5e8a7ce3dabacd5e31fc38786390dfdf73021200ea8aa4b3d6e850226
Timestamp: 1724030843 Timestamp [UCT]: 2024-08-19 01:27:23 Age [y:d:h:m:s]: 00:145:05:30:03
Block: 1090976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103887 RingCT/type: yes/0
Extra: 0157d7e0a5e8a7ce3dabacd5e31fc38786390dfdf73021200ea8aa4b3d6e85022602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eca54378e2eabfc949ec75c5ca8542e585246e8c79723e9a04128534452b703f 0.600000000000 1565601 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": 1090986, "vin": [ { "gen": { "height": 1090976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eca54378e2eabfc949ec75c5ca8542e585246e8c79723e9a04128534452b703f" } } ], "extra": [ 1, 87, 215, 224, 165, 232, 167, 206, 61, 171, 172, 213, 227, 31, 195, 135, 134, 57, 13, 253, 247, 48, 33, 32, 14, 168, 170, 75, 61, 110, 133, 2, 38, 2, 17, 0, 0, 0, 2, 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