Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f602535ae3758eeed6ab9702634bd0554709464e6de2cf8eeb1c11a6048008e

Tx prefix hash: cdd148dc3f0205906870bda5279f3e247d53364e785e1f8b708dcf600793fb10
Tx public key: fc33c6acf99c692256d4668b512e93b21d5f79fe7599e4243196ca19d556c4df
Timestamp: 1695627649 Timestamp [UCT]: 2023-09-25 07:40:49 Age [y:d:h:m:s]: 02:069:04:43:33
Block: 855694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569142 RingCT/type: yes/0
Extra: 01fc33c6acf99c692256d4668b512e93b21d5f79fe7599e4243196ca19d556c4df02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.896872300000 dcy

stealth address amount amount idx
00: 9b317ffe69ad2a8ba6418aafc5de690e8e2febacec39b9c1cab86324c3cbf096 0.896872300000 1309730 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": 855704, "vin": [ { "gen": { "height": 855694 } } ], "vout": [ { "amount": 896872300, "target": { "key": "9b317ffe69ad2a8ba6418aafc5de690e8e2febacec39b9c1cab86324c3cbf096" } } ], "extra": [ 1, 252, 51, 198, 172, 249, 156, 105, 34, 86, 212, 102, 139, 81, 46, 147, 178, 29, 95, 121, 254, 117, 153, 228, 36, 49, 150, 202, 25, 213, 86, 196, 223, 2, 17, 0, 0, 0, 10, 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