Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe3bc4ef1ba8e2012d2aa0e39ca87e730010e5a6b0191f75f72e36661d329a68

Tx prefix hash: 7028759954f21efcf13a60923c04aa35932998ec8a7f7bd8c7acca855d18a676
Tx public key: df56b636790a0f1269f882f1ba697322decaade1bf7a21d9c561fe9169786fbb
Timestamp: 1728546919 Timestamp [UCT]: 2024-10-10 07:55:19 Age [y:d:h:m:s]: 01:038:09:44:07
Block: 1128414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285828 RingCT/type: yes/0
Extra: 01df56b636790a0f1269f882f1ba697322decaade1bf7a21d9c561fe9169786fbb02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d845e3d3e363b24290c06ea44e4e3f8b6a3ac3d24d6e5c4f5ccb7e06790fb82 0.600000000000 1611231 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": 1128424, "vin": [ { "gen": { "height": 1128414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d845e3d3e363b24290c06ea44e4e3f8b6a3ac3d24d6e5c4f5ccb7e06790fb82" } } ], "extra": [ 1, 223, 86, 182, 54, 121, 10, 15, 18, 105, 248, 130, 241, 186, 105, 115, 34, 222, 202, 173, 225, 191, 122, 33, 217, 197, 97, 254, 145, 105, 120, 111, 187, 2, 17, 0, 0, 0, 2, 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