Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d6b7a7d7a5c3ff5b03d037ac387fc3af96a0c0e882271671341792180bc89a9

Tx prefix hash: 5a1b5dee3b2bb34696049ad39597f5effcc5e0d5a95d466a21c9b6f79455c2cf
Tx public key: 338c0876702722b590757d99118ba0ce4cc83ecf36c87878dc4d55ee6a7069bb
Timestamp: 1674249511 Timestamp [UCT]: 2023-01-20 21:18:31 Age [y:d:h:m:s]: 01:364:19:55:30
Block: 679135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521716 RingCT/type: yes/0
Extra: 01338c0876702722b590757d99118ba0ce4cc83ecf36c87878dc4d55ee6a7069bb0211000000035029cbac000000000000000000

1 output(s) for total of 3.449401648000 dcy

stealth address amount amount idx
00: 3fdebd1b4a6c49e42c59e7703a8366da765fad6ec28f4d2a0d0688d0f2df0b11 3.449401648000 1121098 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": 679145, "vin": [ { "gen": { "height": 679135 } } ], "vout": [ { "amount": 3449401648, "target": { "key": "3fdebd1b4a6c49e42c59e7703a8366da765fad6ec28f4d2a0d0688d0f2df0b11" } } ], "extra": [ 1, 51, 140, 8, 118, 112, 39, 34, 181, 144, 117, 125, 153, 17, 139, 160, 206, 76, 200, 62, 207, 54, 200, 120, 120, 220, 77, 85, 238, 106, 112, 105, 187, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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