Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f225394a73fbd106e723b136312993518b999c7f1aac52a8c29b28773cb786cc

Tx prefix hash: 94646f3baef463eb86c377be4922abba159731636d8b9c28b44e8e29e2b43ccb
Tx public key: d8cf3d9d6fa4f9746d8273d988acd7a2fa5c6ea36e89aa15222699e6880b7df2
Timestamp: 1721514478 Timestamp [UCT]: 2024-07-20 22:27:58 Age [y:d:h:m:s]: 00:271:10:58:00
Block: 1070112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193939 RingCT/type: yes/0
Extra: 01d8cf3d9d6fa4f9746d8273d988acd7a2fa5c6ea36e89aa15222699e6880b7df202110000001491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5faeb1abbe5bb0194a4b1789116df14074bf1d4e563ece2ec9ba0dbf18783473 0.600000000000 1541811 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": 1070122, "vin": [ { "gen": { "height": 1070112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5faeb1abbe5bb0194a4b1789116df14074bf1d4e563ece2ec9ba0dbf18783473" } } ], "extra": [ 1, 216, 207, 61, 157, 111, 164, 249, 116, 109, 130, 115, 217, 136, 172, 215, 162, 250, 92, 110, 163, 110, 137, 170, 21, 34, 38, 153, 230, 136, 11, 125, 242, 2, 17, 0, 0, 0, 20, 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