Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e271621c1e67329517cf869712231ea12705a1c6c3f01d669ad98f6015cffbff

Tx prefix hash: 33415612199fb2548a7a976ed92fc539bd7ebfdead897e928085ac1965e100a3
Tx public key: f0b8f0bb4f03cb233bb7816337e6b1ab728143ed0a8f5c295cfa4b96261159d4
Timestamp: 1702369622 Timestamp [UCT]: 2023-12-12 08:27:02 Age [y:d:h:m:s]: 01:040:02:06:50
Block: 911398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289958 RingCT/type: yes/0
Extra: 01f0b8f0bb4f03cb233bb7816337e6b1ab728143ed0a8f5c295cfa4b96261159d402110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41b83577914699b75c53b80e02a907e0c5f0cc469abdff99b07dcc121c0a2f94 0.600000000000 1368600 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": 911408, "vin": [ { "gen": { "height": 911398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41b83577914699b75c53b80e02a907e0c5f0cc469abdff99b07dcc121c0a2f94" } } ], "extra": [ 1, 240, 184, 240, 187, 79, 3, 203, 35, 59, 183, 129, 99, 55, 230, 177, 171, 114, 129, 67, 237, 10, 143, 92, 41, 92, 250, 75, 150, 38, 17, 89, 212, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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