Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e70bba523dc2fa67e5d1cdc3ec7fca7f90949815df727d3ce5b246df4da6a1c5

Tx prefix hash: 408ce167503935776185737a05aa75bfab933c7a17d2d6b4d5a57912599335d1
Tx public key: 1d1f8484a0942e43df3dc4f9595ec1393a8302acf3d554609a42a17398790cc3
Timestamp: 1730627858 Timestamp [UCT]: 2024-11-03 09:57:38 Age [y:d:h:m:s]: 00:143:02:35:02
Block: 1145586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102092 RingCT/type: yes/0
Extra: 011d1f8484a0942e43df3dc4f9595ec1393a8302acf3d554609a42a17398790cc30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f83992290ae5c9c6163c033351a5c29bb8f7f39ce77fecf40612f9478ac77394 0.600000000000 1630051 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": 1145596, "vin": [ { "gen": { "height": 1145586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f83992290ae5c9c6163c033351a5c29bb8f7f39ce77fecf40612f9478ac77394" } } ], "extra": [ 1, 29, 31, 132, 132, 160, 148, 46, 67, 223, 61, 196, 249, 89, 94, 193, 57, 58, 131, 2, 172, 243, 213, 84, 96, 154, 66, 161, 115, 152, 121, 12, 195, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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