Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70bb5353748660c2addd063a6db9bec626d7261b7f52a0656fded73bdc99b759

Tx prefix hash: 7e59eb4d3cb17a9a1344e91ad3a04583c183cbd16d4f6540c2daed44b5422e4e
Tx public key: b8bbf203d7a8a0f5c1e868293fb4de1a4fdf1f4a7ac56e30ee062819c35735fb
Timestamp: 1738948677 Timestamp [UCT]: 2025-02-07 17:17:57 Age [y:d:h:m:s]: 00:286:01:40:23
Block: 1214218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202212 RingCT/type: yes/0
Extra: 01b8bbf203d7a8a0f5c1e868293fb4de1a4fdf1f4a7ac56e30ee062819c35735fb021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 731e6f95bfc36ddaae7d44b3ecb701501c27f5ddfd9af8d6f7accf6342dfabe0 0.600000000000 1701005 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": 1214228, "vin": [ { "gen": { "height": 1214218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "731e6f95bfc36ddaae7d44b3ecb701501c27f5ddfd9af8d6f7accf6342dfabe0" } } ], "extra": [ 1, 184, 187, 242, 3, 215, 168, 160, 245, 193, 232, 104, 41, 63, 180, 222, 26, 79, 223, 31, 74, 122, 197, 110, 48, 238, 6, 40, 25, 195, 87, 53, 251, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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