Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaf0fa64342dcf28e197eeb484473d477f60f8ded5ab1f3b35a16e1f87d9f960

Tx prefix hash: b33c026e4fd87bbaadea5a6206ec0d6148139e07a14bc436752ee182de26afd1
Tx public key: d66e92a778de4b04a9c22a9067f927fb936c92e30cc21cd3cae64585a4039c5b
Timestamp: 1713872233 Timestamp [UCT]: 2024-04-23 11:37:13 Age [y:d:h:m:s]: 01:225:17:14:06
Block: 1006756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420004 RingCT/type: yes/0
Extra: 01d66e92a778de4b04a9c22a9067f927fb936c92e30cc21cd3cae64585a4039c5b02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f903b1cd3383ed21c4fa981221af7e3f219496f19c78f3428719a7188bb8c993 0.600000000000 1467882 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": 1006766, "vin": [ { "gen": { "height": 1006756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f903b1cd3383ed21c4fa981221af7e3f219496f19c78f3428719a7188bb8c993" } } ], "extra": [ 1, 214, 110, 146, 167, 120, 222, 75, 4, 169, 194, 42, 144, 103, 249, 39, 251, 147, 108, 146, 227, 12, 194, 28, 211, 202, 230, 69, 133, 164, 3, 156, 91, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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