Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad4b42ac52b5ccfe40c066f4ae43cdfb7d389dfde615bc3f4194b6757bb81367

Tx prefix hash: b3ec2ea666db92c6fd45bc45010f45d8775678e7967419b446e404514f9ff058
Tx public key: 71b0a142a2e048b3e8446c833dc779c8bd52a5a5a218eba275b143f0a299f56d
Timestamp: 1696085458 Timestamp [UCT]: 2023-09-30 14:50:58 Age [y:d:h:m:s]: 01:238:04:37:11
Block: 859494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431327 RingCT/type: yes/0
Extra: 0171b0a142a2e048b3e8446c833dc779c8bd52a5a5a218eba275b143f0a299f56d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.871243654000 dcy

stealth address amount amount idx
00: 95cc23a52c467af9837bd3b3e1614eacf42bca3ae7dd8e8f527e7be4318789ea 0.871243654000 1313722 of 0

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": 859504, "vin": [ { "gen": { "height": 859494 } } ], "vout": [ { "amount": 871243654, "target": { "key": "95cc23a52c467af9837bd3b3e1614eacf42bca3ae7dd8e8f527e7be4318789ea" } } ], "extra": [ 1, 113, 176, 161, 66, 162, 224, 72, 179, 232, 68, 108, 131, 61, 199, 121, 200, 189, 82, 165, 165, 162, 24, 235, 162, 117, 177, 67, 240, 162, 153, 245, 109, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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