Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afe82ffbf5225c3be260c103f59afda04e2cb6819a3d5339d0154eb6646d6d09

Tx prefix hash: ac66035644699bc54f8bf0fc5f4a1b62bc5480a65fa8292e854d8ecec29bd2ea
Tx public key: 6cbc337a553b10fd7ffd4371fa5870ad8f7e86a1d4dc311f98206cc91b7499a4
Timestamp: 1699600282 Timestamp [UCT]: 2023-11-10 07:11:22 Age [y:d:h:m:s]: 01:070:04:53:48
Block: 888438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311575 RingCT/type: yes/0
Extra: 016cbc337a553b10fd7ffd4371fa5870ad8f7e86a1d4dc311f98206cc91b7499a4021100000003faf35c9c000000000000000000

1 output(s) for total of 0.698612092000 dcy

stealth address amount amount idx
00: 2e9db5bdefa4ab84455546255d560e48fb169276da7f626ae93bef220199c509 0.698612092000 1344377 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": 888448, "vin": [ { "gen": { "height": 888438 } } ], "vout": [ { "amount": 698612092, "target": { "key": "2e9db5bdefa4ab84455546255d560e48fb169276da7f626ae93bef220199c509" } } ], "extra": [ 1, 108, 188, 51, 122, 85, 59, 16, 253, 127, 253, 67, 113, 250, 88, 112, 173, 143, 126, 134, 161, 212, 220, 49, 31, 152, 32, 108, 201, 27, 116, 153, 164, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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