Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbe9175f0f98544a9f2ae56deb23bc41c961c0cc0d025b396db47242864472d8

Tx prefix hash: 72effadc1462fb5768f37ee622351f98489b4dfa369dc4434c0a85c12fe5ca4d
Tx public key: 0fda6b90db264d51c7e14c4e6ab4be41071df484030dd2d7224194fbdd0a64af
Timestamp: 1724852284 Timestamp [UCT]: 2024-08-28 13:38:04 Age [y:d:h:m:s]: 00:088:09:38:26
Block: 1097776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63233 RingCT/type: yes/0
Extra: 010fda6b90db264d51c7e14c4e6ab4be41071df484030dd2d7224194fbdd0a64af02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0535f8e4d3f2ee4bf9fd09e40ced8f0ae0c07c6f03202990f01f84aceec25d40 0.600000000000 1573263 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": 1097786, "vin": [ { "gen": { "height": 1097776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0535f8e4d3f2ee4bf9fd09e40ced8f0ae0c07c6f03202990f01f84aceec25d40" } } ], "extra": [ 1, 15, 218, 107, 144, 219, 38, 77, 81, 199, 225, 76, 78, 106, 180, 190, 65, 7, 29, 244, 132, 3, 13, 210, 215, 34, 65, 148, 251, 221, 10, 100, 175, 2, 17, 0, 0, 0, 6, 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