Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf86ebfe0e70cd68ecf83bc7e716ff3d94d73b76572a823d3acfe44b8eaf3c01

Tx prefix hash: 5e100f83978c6d6cfcce95abe0f685d89e35e1a39700d3436947a76a46c95f3f
Tx public key: d45fbf2801d85394e9f0c65625767e3c94923d311e3a4f1b0535ae0f73c15961
Timestamp: 1745672969 Timestamp [UCT]: 2025-04-26 13:09:29 Age [y:d:h:m:s]: 00:271:17:31:49
Block: 1269886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191864 RingCT/type: yes/0
Extra: 01d45fbf2801d85394e9f0c65625767e3c94923d311e3a4f1b0535ae0f73c1596102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 411ab190ebffdc6deff0b8f6a9fca34263d202bf1d11fe2c1b6fafc787b61647 0.600000000000 1757125 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": 1269896, "vin": [ { "gen": { "height": 1269886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "411ab190ebffdc6deff0b8f6a9fca34263d202bf1d11fe2c1b6fafc787b61647" } } ], "extra": [ 1, 212, 95, 191, 40, 1, 216, 83, 148, 233, 240, 198, 86, 37, 118, 126, 60, 148, 146, 61, 49, 30, 58, 79, 27, 5, 53, 174, 15, 115, 193, 89, 97, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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