Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 140b9b47deaff43e97c5c3bc64ac2c03a997b5ea768b1d2f1169f9d551472735

Tx prefix hash: e97f5a676968a4b51da67b15493717943f2348fb42493e6e9e16575c08c0cdb9
Tx public key: 7c8516433c387de873e03091d3161c0bc2b2438c6cfeee75e1672555dac9c4df
Timestamp: 1720145945 Timestamp [UCT]: 2024-07-05 02:19:05 Age [y:d:h:m:s]: 00:110:08:57:20
Block: 1058757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79043 RingCT/type: yes/0
Extra: 017c8516433c387de873e03091d3161c0bc2b2438c6cfeee75e1672555dac9c4df02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f38cc265f61e72b46fb5e7bf6a5178ece2f961670036023177cbdb1e1a0cfe2 0.600000000000 1529214 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": 1058767, "vin": [ { "gen": { "height": 1058757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f38cc265f61e72b46fb5e7bf6a5178ece2f961670036023177cbdb1e1a0cfe2" } } ], "extra": [ 1, 124, 133, 22, 67, 60, 56, 125, 232, 115, 224, 48, 145, 211, 22, 28, 11, 194, 178, 67, 140, 108, 254, 238, 117, 225, 103, 37, 85, 218, 201, 196, 223, 2, 17, 0, 0, 0, 2, 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