Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7b2f56f1033bad266b417523abf72662e9ae19838e20e582b20eb69e42cdf5d

Tx prefix hash: e220772abd6a1653ce1879c3b9ad7826551aaca9ceab9966e06a342c12ba8fb5
Tx public key: ba20c87603ea70c8b59c05dcf798e7e1d793258036ec29773669f7db84f3dc83
Timestamp: 1720609441 Timestamp [UCT]: 2024-07-10 11:04:01 Age [y:d:h:m:s]: 00:196:01:56:38
Block: 1062619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140252 RingCT/type: yes/0
Extra: 01ba20c87603ea70c8b59c05dcf798e7e1d793258036ec29773669f7db84f3dc83021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10867fbb3db1ae8f68fd118734ae59d865e6a0f735a251f9cc95897c0fc34e1f 0.600000000000 1533124 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": 1062629, "vin": [ { "gen": { "height": 1062619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10867fbb3db1ae8f68fd118734ae59d865e6a0f735a251f9cc95897c0fc34e1f" } } ], "extra": [ 1, 186, 32, 200, 118, 3, 234, 112, 200, 181, 156, 5, 220, 247, 152, 231, 225, 215, 147, 37, 128, 54, 236, 41, 119, 54, 105, 247, 219, 132, 243, 220, 131, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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