Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7eb3fbae438d2335e9a444bb2501df2df483336950d332f4ad980e9115e09ee

Tx prefix hash: cc7410d18f3e9c79237415637196cbad1fd2dec817339f7b9fa1f4c62d0265fa
Tx public key: 10d30e915d702a9309e3e752935df78f60223fd3386e8d0470afb6719979d0ed
Timestamp: 1694742596 Timestamp [UCT]: 2023-09-15 01:49:56 Age [y:d:h:m:s]: 01:131:01:28:24
Block: 848339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354954 RingCT/type: yes/0
Extra: 0110d30e915d702a9309e3e752935df78f60223fd3386e8d0470afb6719979d0ed0211000000014b8f5122000000000000000000

1 output(s) for total of 0.948638595000 dcy

stealth address amount amount idx
00: 2c648a428f0a14ec72d9f667cde3be938053d2362561a4b1e0d5935a062e6241 0.948638595000 1301935 of 0

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": 848349, "vin": [ { "gen": { "height": 848339 } } ], "vout": [ { "amount": 948638595, "target": { "key": "2c648a428f0a14ec72d9f667cde3be938053d2362561a4b1e0d5935a062e6241" } } ], "extra": [ 1, 16, 211, 14, 145, 93, 112, 42, 147, 9, 227, 231, 82, 147, 93, 247, 143, 96, 34, 63, 211, 56, 110, 141, 4, 112, 175, 182, 113, 153, 121, 208, 237, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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