Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd7d70e379e14e1fbde72a8f89de00d6925212ef18db66d3a4e3034332203909

Tx prefix hash: 27990bbfc85fae5b20bcd3759f7025a0438082caa6247a1e1948a6bcf7904f37
Tx public key: 283c518e4c7127d8ec370fe87966be4da3f2753301c3d3544efd5c48f92c2fc7
Timestamp: 1728694868 Timestamp [UCT]: 2024-10-12 01:01:08 Age [y:d:h:m:s]: 00:175:18:11:20
Block: 1129648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125385 RingCT/type: yes/0
Extra: 01283c518e4c7127d8ec370fe87966be4da3f2753301c3d3544efd5c48f92c2fc702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89a79520f1d05ae5818748949bbd7fd1e3a455a3d24145b6d4a4ac8656b1b4d2 0.600000000000 1612481 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": 1129658, "vin": [ { "gen": { "height": 1129648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89a79520f1d05ae5818748949bbd7fd1e3a455a3d24145b6d4a4ac8656b1b4d2" } } ], "extra": [ 1, 40, 60, 81, 142, 76, 113, 39, 216, 236, 55, 15, 232, 121, 102, 190, 77, 163, 242, 117, 51, 1, 195, 211, 84, 78, 253, 92, 72, 249, 44, 47, 199, 2, 17, 0, 0, 0, 3, 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