Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8a14c82071535f17f667c6aed4e95d0536209e0e97732f45f13f19a3ee50fd2

Tx prefix hash: 2081243f4ed117bb07ade5cf7c2c4e3ad23d13a0d7d3c48b2e29f3f929891184
Tx public key: d09301222d5bd528d1fd337ef74763e64699910afae997aae689c0fc5dc05662
Timestamp: 1713937525 Timestamp [UCT]: 2024-04-24 05:45:25 Age [y:d:h:m:s]: 00:218:06:41:14
Block: 1007296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156258 RingCT/type: yes/0
Extra: 01d09301222d5bd528d1fd337ef74763e64699910afae997aae689c0fc5dc056620211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b5899230a8f36668f1d075e80fd84ac10c0f674f62d044ab92243d4e2b9a7c1 0.600000000000 1468590 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": 1007306, "vin": [ { "gen": { "height": 1007296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b5899230a8f36668f1d075e80fd84ac10c0f674f62d044ab92243d4e2b9a7c1" } } ], "extra": [ 1, 208, 147, 1, 34, 45, 91, 213, 40, 209, 253, 51, 126, 247, 71, 99, 230, 70, 153, 145, 10, 250, 233, 151, 170, 230, 137, 192, 252, 93, 192, 86, 98, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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