Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f1eaa9acabf4b4176df034e2180251f46127bdc35186afba024e3143c062776

Tx prefix hash: ab844052e1381f70000b072218f3e33c5a69ec924dcbd4eddb59bdc19496d53b
Tx public key: a1f3d08568c43d8119d76e7de90c74ed6ae53bbb7c9e25662958bf29e0d650d3
Timestamp: 1725757129 Timestamp [UCT]: 2024-09-08 00:58:49 Age [y:d:h:m:s]: 00:123:04:36:23
Block: 1105283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88111 RingCT/type: yes/0
Extra: 01a1f3d08568c43d8119d76e7de90c74ed6ae53bbb7c9e25662958bf29e0d650d302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28d8abc68642383e2bcf970dab6512f2d72bc0c962cea619f843936c80cdbea1 0.600000000000 1582624 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": 1105293, "vin": [ { "gen": { "height": 1105283 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28d8abc68642383e2bcf970dab6512f2d72bc0c962cea619f843936c80cdbea1" } } ], "extra": [ 1, 161, 243, 208, 133, 104, 196, 61, 129, 25, 215, 110, 125, 233, 12, 116, 237, 106, 229, 59, 187, 124, 158, 37, 102, 41, 88, 191, 41, 224, 214, 80, 211, 2, 17, 0, 0, 0, 7, 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