Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03abc79eb1b1f11cc74345483b826b61218d155d2eee0f4d164ddd92357c6e9b

Tx prefix hash: 94fc287d069b7420249eea96d06c493be9451c8dddd9f2b57e995c9670f2b8aa
Tx public key: 970feb7fdaf4cae935213ee2261135a02fa8a0ab874cd6157e25959eeacfb2e7
Timestamp: 1726776436 Timestamp [UCT]: 2024-09-19 20:07:16 Age [y:d:h:m:s]: 01:052:08:36:38
Block: 1113732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295827 RingCT/type: yes/0
Extra: 01970feb7fdaf4cae935213ee2261135a02fa8a0ab874cd6157e25959eeacfb2e702110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04fe55f11ae038944ac2165e9d24d6ab44ae4e92c08849d7611e1cef72b791b6 0.600000000000 1593511 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": 1113742, "vin": [ { "gen": { "height": 1113732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04fe55f11ae038944ac2165e9d24d6ab44ae4e92c08849d7611e1cef72b791b6" } } ], "extra": [ 1, 151, 15, 235, 127, 218, 244, 202, 233, 53, 33, 62, 226, 38, 17, 53, 160, 47, 168, 160, 171, 135, 76, 214, 21, 126, 37, 149, 158, 234, 207, 178, 231, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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