Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1838794d3a800bf3eed094fbbc59b684d8fa1f819d1a133d4121356a71adf716

Tx prefix hash: 8a87bf00502472870ea4e43df965536a4c403dbc9e5e324c36f7a7599c27572e
Tx public key: da00cb69a3cb15a1de3bd589f6f1606fc595efb4b1c9cc2532bf404703838a3b
Timestamp: 1708173928 Timestamp [UCT]: 2024-02-17 12:45:28 Age [y:d:h:m:s]: 01:038:01:58:24
Block: 959507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288232 RingCT/type: yes/0
Extra: 01da00cb69a3cb15a1de3bd589f6f1606fc595efb4b1c9cc2532bf404703838a3b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7ed5a42ede51f0dfed0f5a92024200c7becfb029099acca6483d47d5f047532 0.600000000000 1419044 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": 959517, "vin": [ { "gen": { "height": 959507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7ed5a42ede51f0dfed0f5a92024200c7becfb029099acca6483d47d5f047532" } } ], "extra": [ 1, 218, 0, 203, 105, 163, 203, 21, 161, 222, 59, 213, 137, 246, 241, 96, 111, 197, 149, 239, 180, 177, 201, 204, 37, 50, 191, 64, 71, 3, 131, 138, 59, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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