Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e78c55e235f7e30dcd9b9031f01f6ffdf0fc36cc3d61d1b787ecd06dacacabf

Tx prefix hash: 2bda0fc19fa4c2c8d7351b02ccac4ee0252cd2445f1879ec0429c2f0f918e0d1
Tx public key: e73212b6dfd93743ee38e7007a5b790376888438d50e752284cb1cdb117355a9
Timestamp: 1709332584 Timestamp [UCT]: 2024-03-01 22:36:24 Age [y:d:h:m:s]: 01:264:07:27:26
Block: 969123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447623 RingCT/type: yes/0
Extra: 01e73212b6dfd93743ee38e7007a5b790376888438d50e752284cb1cdb117355a902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af4964ca60048a405bac7836e97c0f05e28fc40e3700b119881e4253d1533a9f 0.600000000000 1428950 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": 969133, "vin": [ { "gen": { "height": 969123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af4964ca60048a405bac7836e97c0f05e28fc40e3700b119881e4253d1533a9f" } } ], "extra": [ 1, 231, 50, 18, 182, 223, 217, 55, 67, 238, 56, 231, 0, 122, 91, 121, 3, 118, 136, 132, 56, 213, 14, 117, 34, 132, 203, 28, 219, 17, 115, 85, 169, 2, 17, 0, 0, 0, 2, 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