Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0747142a0d593c9b4254fdb825a327c5dee34da1987d619359291902698f6e35

Tx prefix hash: 22f8eb94cfe9ca2606e06d7abfe3782e6d24fb858fc8241bf8828fc52c792f65
Tx public key: 7e122ba84e0c1e2e06eb98a8cbd139a43ecaafbd8e09c999c5aa4e1c9efed7f3
Timestamp: 1754683696 Timestamp [UCT]: 2025-08-08 20:08:16 Age [y:d:h:m:s]: 00:103:12:10:47
Block: 1343034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73080 RingCT/type: yes/0
Extra: 017e122ba84e0c1e2e06eb98a8cbd139a43ecaafbd8e09c999c5aa4e1c9efed7f3021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7c3f92dee350a4be884af91c3e2fa159950fbfbf9947cbf4a6ad535f8922097 0.600000000000 1830869 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": 1343044, "vin": [ { "gen": { "height": 1343034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7c3f92dee350a4be884af91c3e2fa159950fbfbf9947cbf4a6ad535f8922097" } } ], "extra": [ 1, 126, 18, 43, 168, 78, 12, 30, 46, 6, 235, 152, 168, 203, 209, 57, 164, 62, 202, 175, 189, 142, 9, 201, 153, 197, 170, 78, 28, 158, 254, 215, 243, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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