Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f8fa6c09409003afa595c97aa186318ce8d5fc618a680e8f483d05d8f17a22f

Tx prefix hash: 0d31b83361dbf92e6fd887c3954dd34c4f22e2fb77397b09d375fad15150b19c
Tx public key: 6935797dbfb421e939fe1d6aa79bcf9112616968d54d43cb7b67195107e9a6cb
Timestamp: 1734303053 Timestamp [UCT]: 2024-12-15 22:50:53 Age [y:d:h:m:s]: 00:136:21:40:34
Block: 1176045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97626 RingCT/type: yes/0
Extra: 016935797dbfb421e939fe1d6aa79bcf9112616968d54d43cb7b67195107e9a6cb0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab1d3463c10422cb72dd4a8c5853327bd81f8de3e3b04e1ed64bb304a5370ca5 0.600000000000 1662374 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": 1176055, "vin": [ { "gen": { "height": 1176045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab1d3463c10422cb72dd4a8c5853327bd81f8de3e3b04e1ed64bb304a5370ca5" } } ], "extra": [ 1, 105, 53, 121, 125, 191, 180, 33, 233, 57, 254, 29, 106, 167, 155, 207, 145, 18, 97, 105, 104, 213, 77, 67, 203, 123, 103, 25, 81, 7, 233, 166, 203, 2, 17, 0, 0, 0, 1, 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