Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38826c421916b53fc97c1514a292e53b9a55a5364c0c8cd28fc8ad35cb68c624

Tx prefix hash: bb8b18605421a0dd7cdbf91a9f4318495050dac49434182e7bd1467d1817e8e0
Tx public key: 8e5a3f38a05efcc5d6afad301ba05554a1a7b7179833c38d88c86967d3b0b05b
Timestamp: 1737385190 Timestamp [UCT]: 2025-01-20 14:59:50 Age [y:d:h:m:s]: 00:304:06:50:28
Block: 1201487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215025 RingCT/type: yes/0
Extra: 018e5a3f38a05efcc5d6afad301ba05554a1a7b7179833c38d88c86967d3b0b05b021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e022b48cdb4c3972f0c8c1a92fdb808359caf9408ba190de60a888d08ccb23ad 0.600000000000 1688140 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": 1201497, "vin": [ { "gen": { "height": 1201487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e022b48cdb4c3972f0c8c1a92fdb808359caf9408ba190de60a888d08ccb23ad" } } ], "extra": [ 1, 142, 90, 63, 56, 160, 94, 252, 197, 214, 175, 173, 48, 27, 160, 85, 84, 161, 167, 183, 23, 152, 51, 195, 141, 136, 200, 105, 103, 211, 176, 176, 91, 2, 17, 0, 0, 0, 1, 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