Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f58093007a20449cc079bb8ecdaf99bf20d199cfe07dcfccf65a4d032fe1c800

Tx prefix hash: 684a0fe0f2e5e34f0853846ab0191ede207c383ecd53dea3182ed8392c8d46dc
Tx public key: 42286a5bf1ebfd202cfcd3edab4d976f6d9dda73f9f16ebfc08f52d87010f1a5
Timestamp: 1722574283 Timestamp [UCT]: 2024-08-02 04:51:23 Age [y:d:h:m:s]: 00:246:18:38:49
Block: 1078893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176271 RingCT/type: yes/0
Extra: 0142286a5bf1ebfd202cfcd3edab4d976f6d9dda73f9f16ebfc08f52d87010f1a5021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9d7023f2c7ca1cfb0dd329d4ab0446625bd1d1303ae513c02b1fac8a866f09b 0.600000000000 1551618 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": 1078903, "vin": [ { "gen": { "height": 1078893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9d7023f2c7ca1cfb0dd329d4ab0446625bd1d1303ae513c02b1fac8a866f09b" } } ], "extra": [ 1, 66, 40, 106, 91, 241, 235, 253, 32, 44, 252, 211, 237, 171, 77, 151, 111, 109, 157, 218, 115, 249, 241, 110, 191, 192, 143, 82, 216, 112, 16, 241, 165, 2, 17, 0, 0, 0, 1, 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