Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf21143b32651b71532bcb15412ae43ce1bf94e2a1830f45638c4d153fad63c4

Tx prefix hash: 59e002e511f88875ebc4f13c1f59551e4ac1fb1e26f51bf0631fb48b895b804c
Tx public key: f780ae7db8511aab60bccb84d20db1e7b2bfc502b174e0cadc9c53a8ccab162a
Timestamp: 1721418629 Timestamp [UCT]: 2024-07-19 19:50:29 Age [y:d:h:m:s]: 00:280:07:05:57
Block: 1069341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200232 RingCT/type: yes/0
Extra: 01f780ae7db8511aab60bccb84d20db1e7b2bfc502b174e0cadc9c53a8ccab162a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82dbb9a3acd19aed1628dfdaaf59ede15d9f3e6f377ccd4988dba6bba9737a58 0.600000000000 1540726 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": 1069351, "vin": [ { "gen": { "height": 1069341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82dbb9a3acd19aed1628dfdaaf59ede15d9f3e6f377ccd4988dba6bba9737a58" } } ], "extra": [ 1, 247, 128, 174, 125, 184, 81, 26, 171, 96, 188, 203, 132, 210, 13, 177, 231, 178, 191, 197, 2, 177, 116, 224, 202, 220, 156, 83, 168, 204, 171, 22, 42, 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