Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e641d0b745b7b09a49a6a9c9b604a0a176cef5429d5dba015da487b4a6ba2e37

Tx prefix hash: ad06609fef5e9cd6da35ae7579cfeafe8542d09ad842426b78264fab4e779eb3
Tx public key: 9bd3dda0fb8a5338bfcef437b22dea89f35e7e29a57a0a2e214101c49db83f94
Timestamp: 1696678534 Timestamp [UCT]: 2023-10-07 11:35:34 Age [y:d:h:m:s]: 01:173:18:01:11
Block: 864406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385218 RingCT/type: yes/0
Extra: 019bd3dda0fb8a5338bfcef437b22dea89f35e7e29a57a0a2e214101c49db83f94021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.839197392000 dcy

stealth address amount amount idx
00: 1b0599f6a3c61b3cbfe8dcad14bd2a5d1b36eddcbe8c1ea010d64a76e3593e49 0.839197392000 1318920 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": 864416, "vin": [ { "gen": { "height": 864406 } } ], "vout": [ { "amount": 839197392, "target": { "key": "1b0599f6a3c61b3cbfe8dcad14bd2a5d1b36eddcbe8c1ea010d64a76e3593e49" } } ], "extra": [ 1, 155, 211, 221, 160, 251, 138, 83, 56, 191, 206, 244, 55, 178, 45, 234, 137, 243, 94, 126, 41, 165, 122, 10, 46, 33, 65, 1, 196, 157, 184, 63, 148, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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