Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdff067bea34099a623fb9ff87f33f7f6481dd48dbc27d5eed8cfb769f57ed58

Tx prefix hash: 02e6b32b0f895e931d290f7f069c8613bf939264caf33a267eb37ca1bc413b46
Tx public key: 98f9753de766acc3bf35d341436d0bf0cddc9c23155991d55bec0fce29e9d1de
Timestamp: 1735545529 Timestamp [UCT]: 2024-12-30 07:58:49 Age [y:d:h:m:s]: 00:110:02:55:52
Block: 1186297 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78501 RingCT/type: yes/0
Extra: 0198f9753de766acc3bf35d341436d0bf0cddc9c23155991d55bec0fce29e9d1de021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 740d14ff6cecd3dac5006499ee3844f7ddd4c0a093f3a650c50478d6d7c9defd 0.600000000000 1672776 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": 1186307, "vin": [ { "gen": { "height": 1186297 } } ], "vout": [ { "amount": 600000000, "target": { "key": "740d14ff6cecd3dac5006499ee3844f7ddd4c0a093f3a650c50478d6d7c9defd" } } ], "extra": [ 1, 152, 249, 117, 61, 231, 102, 172, 195, 191, 53, 211, 65, 67, 109, 11, 240, 205, 220, 156, 35, 21, 89, 145, 213, 91, 236, 15, 206, 41, 233, 209, 222, 2, 17, 0, 0, 0, 2, 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