Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d104f66b34ab116ef3edc481d2fb9c97a0d12c2fde9f65cfeeccd225ed2cbfa

Tx prefix hash: e97d38ea210d8abb566c6f3eb84001f83cb356a00243c68e3391727e5b48d82a
Tx public key: e8eba505ea5e8a0e3910f788e518e273ace8c296b496bd66119d11e4ebaf531c
Timestamp: 1736975913 Timestamp [UCT]: 2025-01-15 21:18:33 Age [y:d:h:m:s]: 00:341:03:06:56
Block: 1198143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241361 RingCT/type: yes/0
Extra: 01e8eba505ea5e8a0e3910f788e518e273ace8c296b496bd66119d11e4ebaf531c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 077f20a9f1bc2e666ade98d73a74b4be571578ce0e7a850194790d45f9d28ebf 0.600000000000 1684762 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": 1198153, "vin": [ { "gen": { "height": 1198143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "077f20a9f1bc2e666ade98d73a74b4be571578ce0e7a850194790d45f9d28ebf" } } ], "extra": [ 1, 232, 235, 165, 5, 234, 94, 138, 14, 57, 16, 247, 136, 229, 24, 226, 115, 172, 232, 194, 150, 180, 150, 189, 102, 17, 157, 17, 228, 235, 175, 83, 28, 2, 17, 0, 0, 0, 3, 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