Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2e58541b59e6f286bf686a0a94ca30e445d2d733762d108f029657779093339

Tx prefix hash: f77789e882a23ae59cb21361a991a8fecb29f6c2437266687a85a5c7a8e1196c
Tx public key: 4bfcc5f2716164226cde9f9ea38581e4b7b5c2cab9ee112bc4612dcb25ab87e8
Timestamp: 1673426787 Timestamp [UCT]: 2023-01-11 08:46:27 Age [y:d:h:m:s]: 02:045:18:40:40
Block: 672304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554354 RingCT/type: yes/0
Extra: 014bfcc5f2716164226cde9f9ea38581e4b7b5c2cab9ee112bc4612dcb25ab87e8021100000001b3e1cbca000000000000000000

1 output(s) for total of 3.633939689000 dcy

stealth address amount amount idx
00: 2d8bcd7918b3a1d86158a7d095fe3b23d7fe35e4c0255f96274522f3c586fd4f 3.633939689000 1113831 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": 672314, "vin": [ { "gen": { "height": 672304 } } ], "vout": [ { "amount": 3633939689, "target": { "key": "2d8bcd7918b3a1d86158a7d095fe3b23d7fe35e4c0255f96274522f3c586fd4f" } } ], "extra": [ 1, 75, 252, 197, 242, 113, 97, 100, 34, 108, 222, 159, 158, 163, 133, 129, 228, 183, 181, 194, 202, 185, 238, 17, 43, 196, 97, 45, 203, 37, 171, 135, 232, 2, 17, 0, 0, 0, 1, 179, 225, 203, 202, 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