Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73ab0e2c50bf08bc8afed6f8bac741311a5dd06720681a9809e8dd204cb1d6c0

Tx prefix hash: 5e8feb5451b29a1de7421911262caa340a98326fbb6b6e702cd43d4e48d05f5f
Tx public key: 9140356b40a28e3ce054541fe2f6927942fda81c10cb234106d185b5a6cc33ab
Timestamp: 1723305192 Timestamp [UCT]: 2024-08-10 15:53:12 Age [y:d:h:m:s]: 01:059:07:13:13
Block: 1084958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300799 RingCT/type: yes/0
Extra: 019140356b40a28e3ce054541fe2f6927942fda81c10cb234106d185b5a6cc33ab02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3f5f62da239571856cb2d2371c60c5c73f9b40d0d0cdb89eebc9151b59f7f45 0.600000000000 1559417 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": 1084968, "vin": [ { "gen": { "height": 1084958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3f5f62da239571856cb2d2371c60c5c73f9b40d0d0cdb89eebc9151b59f7f45" } } ], "extra": [ 1, 145, 64, 53, 107, 64, 162, 142, 60, 224, 84, 84, 31, 226, 246, 146, 121, 66, 253, 168, 28, 16, 203, 35, 65, 6, 209, 133, 181, 166, 204, 51, 171, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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